Thanks Prashant -Jyoti
On Wed, Oct 23, 2013 at 7:52 PM, Prashant Upadhyaya < prashant.upadhyaya at 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 at dpdk.org] On Behalf Of Jyotiswarup Raiturkar > Sent: Wednesday, October 23, 2013 5:10 PM > To: dev at 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. > > =============================================================================== >
