From: "Jayakumar, Muthurajan" <muthurajan.jayakumar@intel.com>
To: Daniel Kan <dan@nyansa.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] What's the performance significance of ixgbe_recv_pkts_bulk_alloc
Date: Sun, 23 Feb 2014 23:57:46 +0000 [thread overview]
Message-ID: <5D695A7F6F10504DBD9B9187395A21797C6E574B@ORSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <71503436-5A40-4097-B1B0-8ED0B9DB6C3E@nyansa.com>
If some one is interested in more of improving throughput, they will want to enable bulk_allocation.
If someone wants to have lesser latency, then they may want to go for non bulk version.
With 10 Gb, it is more critical to use bulk for achieving the desired throughput.
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Daniel Kan
Sent: Sunday, February 23, 2014 3:43 PM
To: dev@dpdk.org
Subject: [dpdk-dev] What's the performance significance of ixgbe_recv_pkts_bulk_alloc
Hi,
While browsing through the ixgbe pmd code, I noticed that there is ixgbe_recv_pkts_bulk_alloc, which can be enabled if the following preconditions are met.
* rxq->rx_free_thresh >= RTE_PMD_IXGBE_RX_MAX_BURST
* rxq->rx_free_thresh < rxq->nb_rx_desc
* (rxq->nb_rx_desc % rxq->rx_free_thresh) == 0
* rxq->nb_rx_desc<(IXGBE_MAX_RING_DESC-RTE_PMD_IXGBE_RX_MAX_BURST)
I presume the difference from the normal (non bulk) version has to do with buffer allocation. Can someone please explain the inner working of bulk_alloc and why one may or may not want to enable bulk_alloc mode?
I only see bulk_alloc is available for ixgbe driver and not igb and e1000. Why is that?
Thanks.
Dan
prev parent reply other threads:[~2014-02-23 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 23:43 Daniel Kan
2014-02-23 23:57 ` Jayakumar, Muthurajan [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=5D695A7F6F10504DBD9B9187395A21797C6E574B@ORSMSX103.amr.corp.intel.com \
--to=muthurajan.jayakumar@intel.com \
--cc=dan@nyansa.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).