From: Simon Horman <simon.horman@corigine.com>
To: Shay Agroskin <shayagr@amazon.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, "Woodhouse, David" <dwmw@amazon.com>,
"Machulsky, Zorik" <zorik@amazon.com>,
"Matushevsky, Alexander" <matua@amazon.com>,
Saeed Bshara <saeedb@amazon.com>, "Wilson, Matt" <msw@amazon.com>,
"Liguori, Anthony" <aliguori@amazon.com>,
"Bshara, Nafea" <nafea@amazon.com>,
"Belgazal, Netanel" <netanel@amazon.com>,
"Saidi, Ali" <alisaidi@amazon.com>,
"Herrenschmidt, Benjamin" <benh@amazon.com>,
"Kiyanovski, Arthur" <akiyano@amazon.com>,
"Dagan, Noam" <ndagan@amazon.com>,
"Arinzon, David" <darinzon@amazon.com>,
"Itzko, Shahar" <itzko@amazon.com>,
"Abboud, Osama" <osamaabb@amazon.com>
Subject: Re: [PATCH RFC v2 net-next 1/4] ethtool: Add support for configuring tx_push_buf_len
Date: Fri, 3 Mar 2023 12:53:51 +0100 [thread overview]
Message-ID: <ZAHfz4iSuNM8XSdU@corigine.com> (raw)
In-Reply-To: <20230302203045.4101652-2-shayagr@amazon.com>
On Thu, Mar 02, 2023 at 10:30:42PM +0200, Shay Agroskin wrote:
> This attribute, which is part of ethtool's ring param configuration
> allows the user to specify the maximum number of the packet's payload
> that can be written directly to the device.
>
> Example usage:
> # ethtool -G [interface] tx-push-buf-len [number of bytes]
>
> Co-developed-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Shay Agroskin <shayagr@amazon.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-03-03 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 20:30 [PATCH RFC v2 net-next 0/4] Add tx push buf len param to ethtool Shay Agroskin
2023-03-02 20:30 ` [PATCH RFC v2 net-next 1/4] ethtool: Add support for configuring tx_push_buf_len Shay Agroskin
2023-03-03 11:53 ` Simon Horman [this message]
2023-03-03 23:50 ` Jakub Kicinski
2023-03-07 10:09 ` Shay Agroskin
2023-03-02 20:30 ` [PATCH RFC v2 net-next 2/4] net: ena: Add an option to configure large LLQ headers Shay Agroskin
2023-03-03 11:51 ` Simon Horman
2023-03-06 9:27 ` Shay Agroskin
2023-03-02 20:30 ` [PATCH RFC v2 net-next 3/4] net: ena: Recalculate TX state variables every device reset Shay Agroskin
2023-03-03 11:53 ` Simon Horman
2023-03-02 20:30 ` [PATCH RFC v2 net-next 4/4] net: ena: Add support to changing tx_push_buf_len Shay Agroskin
2023-03-03 11:54 ` Simon Horman
2023-03-03 23:50 ` Jakub Kicinski
2023-03-06 11:54 ` Shay Agroskin
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=ZAHfz4iSuNM8XSdU@corigine.com \
--to=simon.horman@corigine.com \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.com \
--cc=itzko@amazon.com \
--cc=kuba@kernel.org \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=osamaabb@amazon.com \
--cc=saeedb@amazon.com \
--cc=shayagr@amazon.com \
--cc=zorik@amazon.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).