axi ID problem

Tom T said:

If master send some transaction to different slaves connected to interconnect, is it better to use different ID to different slaves for avoiding deadlock problem?

Don't use same ID to send different slaves?

The interconnect should support the manager using the same AxID to different targets, and so should not be at risk of deadlock.

However, to avoid a deadlock, the interconnect may use some kind of stalling behaviour to ensure the responses are returned in the correct order.  Therefore, it is almost always higher performance to use unique AxIDs.

This is also true for requests to the same target.  A memory controller may be able to respond more efficiently to requests in a different order to what it receives the requests in.  If these have the same AxID, then they must be responded to in order, which would reduce it's efficiency.