From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Yongseok Koh <yskoh@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Requirement of minimum Rx burst size for PMDs
Date: Fri, 20 Oct 2017 15:23:10 +0300 [thread overview]
Message-ID: <56be56b2-092a-ddc1-85ef-6e14065382bd@solarflare.com> (raw)
In-Reply-To: <20171020115823.GA21216@bricha3-MOBL3.ger.corp.intel.com>
On 10/20/2017 02:58 PM, Bruce Richardson wrote:
> On Fri, Oct 20, 2017 at 01:07:17PM +0300, Andrew Rybchenko wrote:
>> On 10/20/2017 04:18 AM, Yongseok Koh wrote:
>>> Therefore, how about adding min_rx/tx_burst_sz in struct rte_eth_dev_info and
>>> have PMDs fill it in on dev_ops->dev_infos_get() so as to make apps comply with
>>> it.
>> Just for my understand, what should happen if application wants to send only
>> one packet? 5 packets? 33? 35?
> I actually think there is a mistake in the original mails. At least for
> Intel PMDs there is no restriction on min TX burst sizes in any code
> path. The vector RX on the other hand does require a minimum number of empty
> buffers to be passed to it, so you need to request no fewer than 4
> packets in a burst. If only one packet is available that will still be
> returned to you, but you must request at least 4
I see. The thread subject says Rx, but Tx (min_tx_burst_sz) is mentioned
above.
If Tx is mentioned by mistake, it is clear now.
Andrew.
next prev parent reply other threads:[~2017-10-20 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 1:18 Yongseok Koh
2017-10-20 8:13 ` Bruce Richardson
2017-10-20 10:07 ` Andrew Rybchenko
2017-10-20 11:58 ` Bruce Richardson
2017-10-20 12:23 ` Andrew Rybchenko [this message]
2017-10-20 16:59 ` Yongseok Koh
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=56be56b2-092a-ddc1-85ef-6e14065382bd@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=yskoh@mellanox.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).