From: Nirmal R <raja.nirmalraj@gmail.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Dpdk multi core packet acquisition.
Date: Wed, 14 Jul 2021 10:32:56 +0200 [thread overview]
Message-ID: <CAPk29mJ0Zt_uUtqWKi-XOp=NBTG66zxT44SMV4Frg-4Y+ReZJg@mail.gmail.com> (raw)
Hello All,
I need to acquire packets from a source at more than 40Gbps. I was thinking
to use rx_burst in a function with more than one core and load it into a
ring. My question is, will the packets received will be in order between
the cores say core 1 receives packet 1,2,3 and core 2 receives packet 4,5,6
or will it be in out of order(Random). Also can we combine 2 cores to
launch one function.
Thank you,
With Regards,
Nirmalraj R
next reply other threads:[~2021-07-14 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 8:32 Nirmal R [this message]
2021-07-14 15:15 ` Stephen Hemminger
2021-07-14 16:32 ` Gábor LENCSE
2021-07-14 17:05 ` Van Haaren, Harry
[not found] ` <CAPk29mLgMP3EaKjLZvAkgz4aUj0U0obQ5+Y60kK7FsUPLy5WaQ@mail.gmail.com>
2021-07-15 8:07 ` Nirmal R
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='CAPk29mJ0Zt_uUtqWKi-XOp=NBTG66zxT44SMV4Frg-4Y+ReZJg@mail.gmail.com' \
--to=raja.nirmalraj@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).