DPDK usage discussions
 help / color / mirror / Atom feed
From: Kevin Kall <fishforish@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Multiple UDP ports Per NIC
Date: Wed, 6 Jun 2018 10:29:57 -0400	[thread overview]
Message-ID: <CAK9TsR0ygQKJVa2sq1hq9SSX_w9EsG=_5gHE5ed+j_zRUC6gmA@mail.gmail.com> (raw)

Hello,

I am brand-new to DPDK (just found out about it) and have what is likely a
simple/stupid question.

Do your libraries/framework allow for different UDP/IP packet streams being
received on a single NIC (different UDP ports) to be directed to/processed
by separate CPU cores (as if each CPU core was opening a different UDP
socket)?

Same goes for transmit - can different CPU cores transmit on separate UDP
ports on a single NIC?

If so, can someone point me to an example?

Thanks so much.

Fish

             reply	other threads:[~2018-06-06 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 14:29 Kevin Kall [this message]
2018-06-07 10:10 ` Richard Nutman
     [not found]   ` <CAK9TsR0GdU6eR27Pz5+nQOHhBM9ZH6GnXecuBL9QsVbXZ4rRSw@mail.gmail.com>
2018-06-07 14:00     ` [dpdk-users] [External] " Richard Nutman

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='CAK9TsR0ygQKJVa2sq1hq9SSX_w9EsG=_5gHE5ed+j_zRUC6gmA@mail.gmail.com' \
    --to=fishforish@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).