netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeed@kernel.org>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, dsahern@gmail.com,
	Jiri Pirko <jiri@nvidia.com>, Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [PATCH iproute2] devlink: Support DEVLINK_ESWITCH_MODE_SWITCHDEV_INACTIVE
Date: Wed, 12 Nov 2025 14:46:10 -0800	[thread overview]
Message-ID: <aRUOMli4cW7XlLFY@x130> (raw)
In-Reply-To: <20251107001435.160260-1-saeed@kernel.org>

On 06 Nov 16:14, Saeed Mahameed wrote:
>From: Saeed Mahameed <saeedm@nvidia.com>
>
>Add support for the new inactive switchdev mode [1].
>
>A user can start the eswitch in switchdev or switchdev_inactive mode.
>
>Active: Traffic is enabled on this eswitch FDB.
>Inactive: Traffic is ignored/dropped on this eswitch FDB.
>
>An example use case:
>$ devlink dev eswitch set pci/0000:08:00.1 mode switchdev_inactive
>Setup FDB pipeline and netdev representors
>...
>Once ready to start receiving traffic
>$ devlink dev eswitch set pci/0000:08:00.1 mode switchdev
>
>[1] https://lore.kernel.org/all/20251107000831.157375-1-saeed@kernel.org/
>

Hi, this was supposed to be marked for -next, do you want me to repost ?

The kernel part was applied to net-next:
https://lore.kernel.org/all/176286361051.3417146.8495442358677824245.git-patchwork-notify@kernel.org/



  reply	other threads:[~2025-11-12 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07  0:14 [PATCH iproute2] devlink: Support DEVLINK_ESWITCH_MODE_SWITCHDEV_INACTIVE Saeed Mahameed
2025-11-12 22:46 ` Saeed Mahameed [this message]
2025-11-12 22:53   ` David Ahern
2025-11-15  1:22 ` David Ahern

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=aRUOMli4cW7XlLFY@x130 \
    --to=saeed@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jiri@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=stephen@networkplumber.org \
    /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).