From: Stephen Hemminger <stephen@networkplumber.org>
To: Joo Kim <itsolution@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] What is the max size of packets rte_eth_tx_burst() can send practically/theoritically?
Date: Tue, 28 Feb 2017 22:24:19 -0800 [thread overview]
Message-ID: <20170228222419.1ced1cb2@xeon-e3> (raw)
In-Reply-To: <CAFj4wcL2PVD3YHArPb7gXmMr_YZoFodaTaEKbU0YtNmk1R3GUw@mail.gmail.com>
On Tue, 28 Feb 2017 20:28:21 -0800
Joo Kim <itsolution@gmail.com> wrote:
> Hello,
>
>
> For example, as I understand, ovs-dpdk code uses a buffer of size 32
> when it transmits via rte_eth_tx_burst().
>
> I think it can transmit more packets in a bust.
> I know there should be a balance between throughput and latency. But, I am
> wondering what max size packets a dpdk application can give to
> rte_eth_tx_burst() practically/theoretically?
> (I see some max macro in ixgbe_rxtx.h)
>
> Thanks
You could theoretically transmit a burst size up to the configured number of TX descriptors.
The downside is you will add latency and have to handle the TX ring getting full more often.
Bigger burst sizes really don't win that much. 50% of the gain happens by just sending 2 at a time.
prev parent reply other threads:[~2017-03-01 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 4:28 Joo Kim
2017-03-01 6:24 ` Stephen Hemminger [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=20170228222419.1ced1cb2@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=itsolution@gmail.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).