From: Jakub Kicinski <kuba@kernel.org>
To: Danielle Ratson <danieller@nvidia.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<yuehaibing@huawei.com>, <linux-kernel@vger.kernel.org>,
<petrm@nvidia.com>
Subject: Re: [PATCH net-next v2 0/2] ethtool: Add support for writing firmware
Date: Sun, 15 Sep 2024 19:17:18 +0200 [thread overview]
Message-ID: <20240915191718.1da2bc78@kernel.org> (raw)
In-Reply-To: <20240910090217.3044324-1-danieller@nvidia.com>
On Tue, 10 Sep 2024 12:02:15 +0300 Danielle Ratson wrote:
> In the CMIS specification for pluggable modules, LPL (Local Payload) and
> EPL (Extended Payload) are two types of data payloads used for managing
> various functions and features of the module.
>
> EPL payloads are used for more complex and extensive management functions
> that require a larger amount of data, so writing firmware blocks using EPL
> is much more efficient.
>
> Currently, only LPL payload is supported for writing firmware blocks to
> the module.
>
> Add support for writing firmware block using EPL payload, both to support
> modules that support only EPL write mechanism, and to optimize the flashing
> process of modules that support LPL and EPL.
>
> Running the flashing command on the same sample module using EPL vs. LPL
> showed an improvement of 84%.
this missed 6.12, sorry, I didn't get a clear enough signal form
the discussion to merge it in time
--
pw-bot: defer
prev parent reply other threads:[~2024-09-15 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 9:02 [PATCH net-next v2 0/2] ethtool: Add support for writing firmware Danielle Ratson
2024-09-10 9:02 ` [PATCH net-next v2 1/2] net: ethtool: Add new parameters and a function to support EPL Danielle Ratson
2024-09-11 7:32 ` Simon Horman
2024-09-10 9:02 ` [PATCH net-next v2 2/2] net: ethtool: Add support for writing firmware blocks using EPL payload Danielle Ratson
2024-09-11 7:32 ` Simon Horman
2024-09-11 12:26 ` Andrew Lunn
2024-09-11 15:41 ` Danielle Ratson
2024-09-11 17:38 ` Andrew Lunn
2024-09-13 7:29 ` Danielle Ratson
2024-09-15 17:17 ` Jakub Kicinski [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=20240915191718.1da2bc78@kernel.org \
--to=kuba@kernel.org \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=yuehaibing@huawei.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).