From: Gal Pressman <gal@nvidia.com>
To: Guangbin Huang <huangguangbin2@huawei.com>,
davem@davemloft.net, kuba@kernel.org, mkubecek@suse.cz,
andrew@lunn.ch, amitc@mellanox.com, idosch@idosch.org,
danieller@nvidia.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, jdike@addtoit.com, richard@nod.at,
anton.ivanov@cambridgegreys.com, netanel@amazon.com,
akiyano@amazon.com, gtzalik@amazon.com, saeedb@amazon.com,
chris.snook@gmail.com, ulli.kroll@googlemail.com,
linus.walleij@linaro.org, jeroendb@google.com, csully@google.com,
awogbemila@google.com, jdmason@kudzu.us,
rain.1986.08.12@gmail.com, zyjzyj2000@gmail.com,
kys@microsoft.com, haiyangz@microsoft.com, mst@redhat.com,
jasowang@redhat.com, doshir@vmware.com, pv-drivers@vmware.com,
jwi@linux.ibm.com, kgraul@linux.ibm.com, hca@linux.ibm.com,
gor@linux.ibm.com, johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, lipeng321@huawei.com,
chenhao288@hisilicon.com, linux-s390@vger.kernel.org
Subject: Re: [PATCH V7 net-next 0/6] ethtool: add support to set/get tx copybreak buf size and rx buf len
Date: Wed, 26 Oct 2022 17:00:01 +0300 [thread overview]
Message-ID: <40d6352e-8c6b-404f-8b6a-df1816239ab0@nvidia.com> (raw)
In-Reply-To: <20211118121245.49842-1-huangguangbin2@huawei.com>
On 18/11/2021 14:12, Guangbin Huang wrote:
> From: Hao Chen <chenhao288@hisilicon.com>
>
> This series add support to set/get tx copybreak buf size and rx buf len via
> ethtool and hns3 driver implements them.
>
> Tx copybreak buf size is used for tx copybreak feature which for small size
> packet or frag. Use ethtool --get-tunable command to get it, and ethtool
> --set-tunable command to set it, examples are as follow:
>
> 1. set tx spare buf size to 102400:
> $ ethtool --set-tunable eth1 tx-buf-size 102400
>
> 2. get tx spare buf size:
> $ ethtool --get-tunable eth1 tx-buf-size
> tx-buf-size: 102400
Hi Guangbin,
Can you please clarify the difference between TX copybreak and TX
copybreak buf size?
next prev parent reply other threads:[~2022-10-26 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 12:12 [PATCH V7 net-next 0/6] ethtool: add support to set/get tx copybreak buf size and rx buf len Guangbin Huang
2021-11-18 12:12 ` [PATCH V7 net-next 1/6] ethtool: add support to set/get tx copybreak buf size via ethtool Guangbin Huang
2021-11-18 12:12 ` [PATCH V7 net-next 2/6] net: hns3: add support to set/get tx copybreak buf size via ethtool for hns3 driver Guangbin Huang
2021-11-18 12:12 ` [PATCH V7 net-next 3/6] ethtool: add support to set/get rx buf len via ethtool Guangbin Huang
2021-11-18 12:12 ` [PATCH V7 net-next 5/6] net: hns3: add support to set/get rx buf len via ethtool for hns3 driver Guangbin Huang
2021-11-18 12:12 ` [PATCH V7 net-next 6/6] net: hns3: remove the way to set tx spare buf via module parameter Guangbin Huang
2021-11-22 13:00 ` [PATCH V7 net-next 0/6] ethtool: add support to set/get tx copybreak buf size and rx buf len patchwork-bot+netdevbpf
2022-10-26 14:00 ` Gal Pressman [this message]
2022-10-27 0:49 ` Yunsheng Lin
2022-10-27 9:03 ` Gal Pressman
2022-10-28 0:50 ` Yunsheng Lin
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=40d6352e-8c6b-404f-8b6a-df1816239ab0@nvidia.com \
--to=gal@nvidia.com \
--cc=akiyano@amazon.com \
--cc=amitc@mellanox.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=awogbemila@google.com \
--cc=chenhao288@hisilicon.com \
--cc=chris.snook@gmail.com \
--cc=csully@google.com \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=doshir@vmware.com \
--cc=gor@linux.ibm.com \
--cc=gtzalik@amazon.com \
--cc=haiyangz@microsoft.com \
--cc=hca@linux.ibm.com \
--cc=huangguangbin2@huawei.com \
--cc=idosch@idosch.org \
--cc=jasowang@redhat.com \
--cc=jdike@addtoit.com \
--cc=jdmason@kudzu.us \
--cc=jeroendb@google.com \
--cc=jesse.brandeburg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=jwi@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linus.walleij@linaro.org \
--cc=linux-s390@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=mkubecek@suse.cz \
--cc=mst@redhat.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=rain.1986.08.12@gmail.com \
--cc=richard@nod.at \
--cc=saeedb@amazon.com \
--cc=ulli.kroll@googlemail.com \
--cc=zyjzyj2000@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