From: Zoltan Kiss <zoltan.kiss@linaro.org>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] ixgbe vPMD RX functions and buffer number minimum requirement
Date: Fri, 24 Jul 2015 15:59:58 +0100 [thread overview]
Message-ID: <55B252EE.9060306@linaro.org> (raw)
Hi,
I was thinking how to handle the situation when you call
rte_eth_rx_burst with less than RTE_IXGBE_VPMD_RX_BURST buffers. In
ODP-DPDK unfortunately we can't force this requirement onto the calling
application.
One idea I had to check in ixgbe_recv_pkts_vec() if nb_pkts <
RTE_IXGBE_VPMD_RX_BURST, and call ixgbe_recv_pkts_bulk_alloc in that
case. Accordingly, in ixgbe_recv_scattered_pkts_vec() we could call
ixgbe_recv_scattered_pkts() in this case. A branch predictor can easily
eliminate the performance penalty of this, and applications can use
whatever burst size feasible for them.
The obvious problem could be whether you can mix the receive functions
this way. I have a feeling it wouldn't fly, but I wanted to ask first
before spending time investigate this option further.
Regards,
Zoltan
next reply other threads:[~2015-07-24 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 14:59 Zoltan Kiss [this message]
2015-07-24 16:43 ` Ananyev, Konstantin
2015-07-27 11:38 ` Zoltan Kiss
2015-07-28 0:10 ` Ananyev, Konstantin
2015-07-28 8:49 ` Liang, Cunming
2015-07-29 9:40 ` Zoltan Kiss
2015-07-29 10:03 ` Ananyev, Konstantin
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=55B252EE.9060306@linaro.org \
--to=zoltan.kiss@linaro.org \
--cc=bruce.richardson@intel.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).