[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dpdk-users
Subject:    re: ports and queues
From:       fwefew 4t4tg <7532yahoo () gmail ! com>
Date:       2022-01-26 1:58:47
Message-ID: CA+Tq66WB3_QGA3OKEPBu5MgX+5mqcT7XUp8=rym44h7b7AotJQ () mail ! gmail ! com
[Download RAW message or body]

Which is the preferred relationship?

* N receive queues share one (TCP/UDP) port whence all TX queues send to
this port

or

* Each transmit queue chooses a TCP/UDP port where, on the RX side, each
receive queue listens on its own port for that queue.

I'm betting it's the second case. However, what also confuses me is that
RSS sits between TX and RX and chooses which RX queue a packet gets into.
It's not deterministically set at TX time. Therefore the recommended
approach appears to actually be:

* Each transmit queue chooses a TCP/UDP port by knowing ahead of time how
RSS will hash the packet for delivery to a certain RX queue.

Thanks

[Attachment #3 (text/html)]

<div dir="ltr">Which is the preferred relationship?<br><br>* N receive queues share \
one (TCP/UDP) port whence all TX queues send to this port<br><br>or<br><br><div>* \
Each transmit queue chooses a TCP/UDP port where, on the RX side, each receive queue \
listens on its own port for that queue.<br><br>I&#39;m betting it&#39;s the second \
case. However, what also confuses me is that RSS sits between TX and RX and chooses \
which RX queue a packet gets into. It&#39;s not deterministically set at TX time. \
Therefore the recommended approach appears to actually be:<br><br>* Each transmit \
queue chooses a TCP/UDP port by knowing ahead of time how RSS will hash the packet \
for delivery to a certain  RX queue.  \
<br></div><div><br></div><div>Thanks</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]