From: Louis Peens <louis.peens@corigine.com>
To: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Jiri Pirko <jiri@resnulli.us>, Fei Qin <fei.qin@corigine.com>,
netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: [PATCH net-next v4 0/4] nfp: series of minor driver improvements
Date: Fri, 5 Apr 2024 10:15:43 +0200 [thread overview]
Message-ID: <20240405081547.20676-1-louis.peens@corigine.com> (raw)
This short series bundles two unrelated but small updates to the nfp
driver.
Patch1: Add new define for devlink string "board.part_number"
Patch2: Make use of this field in the nfp driver
Patch3: Add new 'dim' profiles
Patch4: Make use of these new profiles in the nfp driver
Changes since V3:
- Fixed: Documentation/networking/devlink/devlink-info.rst:150:
WARNING: Title underline too short.
Changes since V2:
- After some discussion on the previous series it was agreed that only
the "board.part_number" field makes sense in the common code. The
"board.model" field which was moved to devlink common code in V1 is
now kept in the driver. The field is specific to the nfp driver,
exposing the codename of the board.
- In summary, add "board.part_number" to devlink, and populate it
in the the nfp driver.
Changes since V1:
- Move nfp local defines to devlink common code as it is quite generic.
- Add new 'dim' profile instead of using driver local overrides, as this
allows use of the 'dim' helpers.
- This expanded 2 patches to 4, as the common code changes are split
into seperate patches.
Fei Qin (4):
devlink: add a new info version tag
nfp: update devlink device info output
dim: introduce a specific dim profile for better latency
nfp: use new dim profiles for better latency
.../networking/devlink/devlink-info.rst | 5 +++++
Documentation/networking/devlink/nfp.rst | 5 ++++-
.../net/ethernet/netronome/nfp/nfp_devlink.c | 1 +
.../ethernet/netronome/nfp/nfp_net_common.c | 4 ++--
include/linux/dim.h | 2 ++
include/net/devlink.h | 4 +++-
lib/dim/net_dim.c | 18 ++++++++++++++++++
7 files changed, 35 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-05 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 8:15 Louis Peens [this message]
2024-04-05 8:15 ` [PATCH net-next v4 1/4] devlink: add a new info version tag Louis Peens
2024-04-08 13:20 ` Simon Horman
2024-04-05 8:15 ` [PATCH net-next v4 2/4] nfp: update devlink device info output Louis Peens
2024-04-08 13:18 ` Simon Horman
2024-04-09 2:58 ` Jakub Kicinski
2024-04-09 7:31 ` Louis Peens
2024-04-05 8:15 ` [PATCH net-next v4 3/4] dim: introduce a specific dim profile for better latency Louis Peens
2024-04-08 13:12 ` Simon Horman
2024-04-09 2:55 ` Jakub Kicinski
2024-04-09 7:33 ` Louis Peens
2024-04-05 8:15 ` [PATCH net-next v4 4/4] nfp: use new dim profiles " Louis Peens
2024-04-08 13:13 ` Simon Horman
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=20240405081547.20676-1-louis.peens@corigine.com \
--to=louis.peens@corigine.com \
--cc=davem@davemloft.net \
--cc=fei.qin@corigine.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.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).