DPDK usage discussions
 help / color / mirror / Atom feed
From: fwefew 4t4tg <7532yahoo@gmail.com>
To: users@dpdk.org
Subject: re: ports and queues
Date: Tue, 25 Jan 2022 21:00:30 -0500	[thread overview]
Message-ID: <CA+Tq66WB3_QGA3OKEPBu5MgX+5mqcT7XUp8=rym44h7b7AotJQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

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 #2: Type: text/html, Size: 753 bytes --]

                 reply	other threads:[~2022-01-26  2:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+Tq66WB3_QGA3OKEPBu5MgX+5mqcT7XUp8=rym44h7b7AotJQ@mail.gmail.com' \
    --to=7532yahoo@gmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).