All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: sthemmin@microsoft.com, dsahern@gmail.com, kuba@kernel.org,
	moshe@nvidia.com, aeedm@nvidia.com
Subject: [patch iproute2-next 0/3] devlink: make ifname-port relationship behaviour better
Date: Fri,  4 Nov 2022 11:23:24 +0100	[thread overview]
Message-ID: <20221104102327.770260-1-jiri@resnulli.us> (raw)

From: Jiri Pirko <jiri@nvidia.com>

This patchset consists of 2 items:
1) patch #1 is fixing output of "devlink mon port" by considering
   possible ifname change during run.
2) patch #3 is benefiting of newly added IFLA_DEVLINK_PORT attribute
   exposing netdev link to devlink port directly. Patch #2 is just
   dependency for patch #3

Jiri Pirko (3):
  devlink: query ifname for devlink port instead of map lookup
  devlink: add ifname_map_add/del() helpers
  devlink: get devlink port for ifname using RTNL get link command

 devlink/devlink.c | 164 +++++++++++++++++++++++++++++++++++++++-------
 1 file changed, 140 insertions(+), 24 deletions(-)

-- 
2.37.3


             reply	other threads:[~2022-11-04 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 10:23 Jiri Pirko [this message]
2022-11-04 10:23 ` [patch iproute2-next 1/3] devlink: query ifname for devlink port instead of map lookup Jiri Pirko
2022-11-07 15:16   ` David Ahern
2022-11-07 15:54     ` Jiri Pirko
2022-11-08 15:59       ` David Ahern
2022-11-09 11:57         ` Jiri Pirko
2022-11-04 10:23 ` [patch iproute2-next 2/3] devlink: add ifname_map_add/del() helpers Jiri Pirko
2022-11-04 10:23 ` [patch iproute2-next 3/3] devlink: get devlink port for ifname using RTNL get link command Jiri Pirko

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=20221104102327.770260-1-jiri@resnulli.us \
    --to=jiri@resnulli.us \
    --cc=aeedm@nvidia.com \
    --cc=dsahern@gmail.com \
    --cc=kuba@kernel.org \
    --cc=moshe@nvidia.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.