DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org
Cc: dev-bounces-VfR2kkLFssw@public.gmane.org,
	dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Lcore-vports-queues mapping
Date: Tue, 17 Feb 2015 10:13:43 +0000	[thread overview]
Message-ID: <20150217101342.GA9356@bricha3-MOBL3> (raw)
In-Reply-To: <SIXPR03MB060587969A66453E5ABFA8F18A2F0-vZpGLg/9lRnmkicDWJed+682SN/2zMuYvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>

On Tue, Feb 17, 2015 at 09:08:07AM +0000, kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org wrote:
> Hi Team ,
> 
> I am using DPDK-1.7.1 , I am trying find out how to map lcore -- >vports -- > queuesin code level as well as user command prompt level .
> Suggestions are welcome on this .
> 
>
Hi,

cores and ports and queues can be mapped just about any way that your application
wants. The only real restriction is that two cores cannot poll the same queue
on the same port at the same time.
You can set up your app to have each port polled by a single core, or to have
all ports polled by one core, or to have one port polled by multiple cores (using
different queues).

Regards,
/Bruce

  parent reply	other threads:[~2015-02-17 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  9:08 Lcore-vports-queues mapping kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w
     [not found] ` <SIXPR03MB060587969A66453E5ABFA8F18A2F0-vZpGLg/9lRnmkicDWJed+682SN/2zMuYvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2015-02-17 10:13   ` Bruce Richardson [this message]
2015-02-17 10:20     ` kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w
     [not found]       ` <SIXPR03MB0605602DAF35EFD0F9FFC1778A2F0-vZpGLg/9lRnmkicDWJed+682SN/2zMuYvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2015-02-17 10:29         ` Bruce Richardson
2015-02-17 10:46           ` kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w

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=20150217101342.GA9356@bricha3-MOBL3 \
    --to=bruce.richardson-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=dev-bounces-VfR2kkLFssw@public.gmane.org \
    --cc=kuldeep.samasi-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.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