From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Long Li <longli@linuxonhyperv.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
Long Li <longli@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH V3 1/2] net/netvsc: allow setting rx and tx copy break
Date: Mon, 2 Nov 2020 10:14:48 +0000 [thread overview]
Message-ID: <0f93ad59-d432-338d-1aed-18b70b3f411c@intel.com> (raw)
In-Reply-To: <1604103849-15879-1-git-send-email-longli@linuxonhyperv.com>
On 10/31/2020 12:24 AM, Long Li wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
>
> The values for Rx and Tx copy break should be tunable rather
> than hard coded constants.
>
> The rx_copybreak sets the threshold where the driver uses an
> external mbuf to avoid having to copy data. Setting 0 for copybreak
> will cause driver to always create an external mbuf. Setting
> a value greater than the MTU would prevent it from ever making
> an external mbuf and always copy. The default value is 256 (bytes).
>
> Likewise the tx_copybreak sets the threshold where the driver
> aggregates multiple small packets into one request. If tx_copybreak
> is 0 then each packet goes as a VMBus request (no copying).
> If tx_copybreak is set larger than the MTU, then all packets smaller
> than the chunk size of the VMBus send buffer will be copied; larger
> packets always have to go as a single direct request. The default
> value is 512 (bytes).
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Signed-off-by: Long Li <longli@microsoft.com>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-11-02 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 0:24 Long Li
2020-10-31 0:24 ` [dpdk-dev] [PATCH V3 2/2] net/netvsc: introduce driver parameter to control the use of external mbuf on receiving data Long Li
2020-11-02 10:14 ` Ferruh Yigit [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=0f93ad59-d432-338d-1aed-18b70b3f411c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).