On Thu, Oct 17, 2024 at 11:36 AM Tudor Ambarus <tudor.ambarus@xxxxxxxxxx> wrote: > > Current form of the mailbox framework doesn't allow controllers to benefit > of their hardware queue capabilities as the framework handles a single > active request at a time. > > The active request is considered completed when TX completes. But it seems > that TX is not in direct relation with RX, > Correct, and it is not meant to be. You are assuming there is always an RX in response to a TX, which is not the case. Many platforms just send a message and only need to know when it is sent. Many platforms only listen for incoming messages. Many platforms have TX and RX but not as parts of one exchange. In fact, only minority of platforms expect RX after each TX. Btw, what if some platform sends only and always after each receive? For these reasons, it is left to the user to tie an incoming RX to some previous TX, or not. Regards. Jassi
