From: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>
To: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] query about port queues
Date: Thu, 24 Oct 2013 10:09:37 +0530 [thread overview]
Message-ID: <CAJn5u1nVB6RNQS7BAR53o-H2_maGJoQMURXnNK92zBqmqjyHhQ@mail.gmail.com> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C43EA7059CF@GUREXMB01.ASIAN.AD.ARICENT.COM>
Thanks Prashant
-Jyoti
On Wed, Oct 23, 2013 at 7:52 PM, Prashant Upadhyaya <
prashant.upadhyaya@aricent.com> wrote:
> Hi Jyoti,
>
> You can configure the number of tx and rx queues via the software when you
> are calling the rte_eth_dev_configure.
> However you cannot allocate more than what the NIC supports. But you can
> allocate less ofcourse.
>
> Typically the queues are used so that independent cores can do tx and rx
> on a separate queue without locking.
>
> If you have configured 'n' rx queues, your must ensure that you read from
> _all_ the queues because the packet can arrive on any of the rx queues
> based on the algorithm by which NIC fans out incoming messages on the
> queues (eg. RSS). You can transmit freely from any queue (eg. each core of
> yours could have a tx queue each in your usecase)
>
> Regards
> -Prashant
>
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jyotiswarup Raiturkar
> Sent: Wednesday, October 23, 2013 5:10 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] query about port queues
>
> Hello Devs
> I'm new to DPDK and trying to understand the basics. I went through the
> programming guide but I had one question regarding Tx and Rx queues per
> port. Are they configurable entirely in software or do they depend on the
> HW (NIC)? Does the L2 configuration (MAC address) apply to all the queues
> on the port? (and hence will an application like say a network stack need
> packets from all the queues in the port)?
> Thanks
> Jyotiswarup Raiturkar
>
>
>
>
>
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
>
> ===============================================================================
>
prev parent reply other threads:[~2013-10-24 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 11:40 Jyotiswarup Raiturkar
2013-10-23 14:22 ` Prashant Upadhyaya
2013-10-24 4:39 ` Jyotiswarup Raiturkar [this message]
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=CAJn5u1nVB6RNQS7BAR53o-H2_maGJoQMURXnNK92zBqmqjyHhQ@mail.gmail.com \
--to=jyotisr5@googlemail.com \
--cc=dev@dpdk.org \
--cc=prashant.upadhyaya@aricent.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).