From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Nishant Verma <vnish11@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Fwd: port-queue-process
Date: Sat, 28 Nov 2015 19:12:24 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C860FFF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAHhCjUH-HPJ_7vq4Funm9i0broyZfCEv-B0Sonq5RVjWy4Rx0A@mail.gmail.com>
Hi Nishant,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nishant Verma
> Sent: Saturday, November 28, 2015 5:42 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Fwd: port-queue-process
>
> Hi All,
>
> I have one doubt about dpdk.
>
> Question. Suppose on 8 core machine DPDK process is running on all cores,
> all process has its own Rx & Tx queue. My question is, let we have a packet
> from some network for DPDK application running on 2nd core, how it will
> reach to 2nd core and not to some other core.
>
> Any clue and reference will be appreciated. It might seems to little doubt
> but as i don't know, its big for me.
I think what you are looking for is packet filtering and queue assignment,
specifically, Flow Director. I assume you have one port and several queues in that port:
you will need assign each queue to a different core, and program the device in a way that
packets with a particular source MAC address or IP address will go to a specified queue,
so the desired core can poll the packets from that queue.
Let me know if you have any more questions,
Pablo
>
> thanks.
>
> --
> Rgds,
>
> NV
next prev parent reply other threads:[~2015-11-28 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHhCjUF9P_gC4eXio8US0=RXcvkhA=_now10JrioP-ft20fK0g@mail.gmail.com>
2015-11-28 5:41 ` Nishant Verma
2015-11-28 19:12 ` De Lara Guarch, Pablo [this message]
2015-11-28 19:27 ` Nishant Verma
2015-11-29 20:43 ` De Lara Guarch, Pablo
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=E115CCD9D858EF4F90C690B0DCB4D8973C860FFF@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=vnish11@gmail.com \
/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).