DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] query about port queues
Date: Wed, 23 Oct 2013 17:10:18 +0530	[thread overview]
Message-ID: <CAJn5u1=Aq9aghQERLbEx35LqZ6U41gXnE9MmYyE6dTPQUuC5HA@mail.gmail.com> (raw)

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

             reply	other threads:[~2013-10-23 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 11:40 Jyotiswarup Raiturkar [this message]
2013-10-23 14:22 ` Prashant Upadhyaya
2013-10-24  4:39   ` Jyotiswarup Raiturkar

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='CAJn5u1=Aq9aghQERLbEx35LqZ6U41gXnE9MmYyE6dTPQUuC5HA@mail.gmail.com' \
    --to=jyotisr5@googlemail.com \
    --cc=dev@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).