From: Jakub Kicinski <kuba@kernel.org>
To: Kiran Kella <kiran.kella@broadcom.com>
Cc: Daniel Zahka <daniel.zahka@gmail.com>,
davem@davemloft.net, edumazet@google.com, willemb@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jayakrishnan.udayavarma@broadcom.com, ajit.khaparde@broadcom.com,
akhilesh.samineni@broadcom.com
Subject: Re: [net-next, v2 1/2] psp: Support for transmit on logical device when the underlying transport device supports PSP.
Date: Thu, 26 Feb 2026 17:06:46 -0800 [thread overview]
Message-ID: <20260226170646.0c4baeb6@kernel.org> (raw)
In-Reply-To: <CAPHeo3eJRYc503Ta24h9r+Uu1cGqb1dCfmnxuZQ4MJLCTFd9Lw@mail.gmail.com>
On Thu, 26 Feb 2026 17:16:58 +0530 Kiran Kella wrote:
> > The lack of support for netns is a bit of a gap for this feature. It may
> > make sense to see if what was posted in
> > https://lore.kernel.org/netdev/20260224002410.1553838-1-weibunny@fb.com/
> > is sufficient for your use case, as it handles cases where upper devices
> > are in a different netns from psd->main_netdev.
>
> Thanks. Went through the changes in
> https://lore.kernel.org/netdev/20260224002410.1553838-1-weibunny@fb.com/
> It is sufficient for my use case too, although it specifically
> addresses the cross-netns virtual devices use case.
> But the same net-ns stacked devices like VLANs can be handled with
> this patch implicitly, without user intervention through dev-assoc.
> I think both approaches can co-exist without conflict.
> However, I am ok with using a single approach to use the dev-assoc for
> the same net-ns use case too.
FTR I have mixed feelings about automatic propagation of PSP onto upper
devices. If we propagate it onto vlan, why not bond, and if bond why not
bridge. Or macsec (can every device do multiple layers of encryption?)
If user does the propagation and that results in packet loss that's
user's fault not ours. IDK.
next prev parent reply other threads:[~2026-02-27 1:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 19:11 [net-next, v2 0/2] psp: Support PSP Tx on logical devices like VLAN Kiran Kella
2026-02-23 19:11 ` [net-next, v2 1/2] psp: Support for transmit on logical device when the underlying transport device supports PSP Kiran Kella
2026-02-24 20:58 ` Daniel Zahka
2026-02-26 11:38 ` Kiran Kella
2026-02-26 11:46 ` Kiran Kella
2026-02-26 14:11 ` Daniel Zahka
2026-02-26 15:11 ` Kiran Kella
2026-02-27 1:06 ` Jakub Kicinski [this message]
2026-02-23 19:11 ` [net-next, v2 2/2] selftests: drv-net: psp: add test for VLAN sub-interface Kiran Kella
2026-02-23 21:58 ` Jakub Kicinski
2026-02-25 7:22 ` Kiran Kella
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=20260226170646.0c4baeb6@kernel.org \
--to=kuba@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=akhilesh.samineni@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jayakrishnan.udayavarma@broadcom.com \
--cc=kiran.kella@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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