From: Jakub Kicinski <kuba@kernel.org>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: brett.creeley@amd.com, netdev@vger.kernel.org, drivers@pensando.io
Subject: Re: [PATCH RFC net-next 0/2] pds_core: add switchdev and tc for vlan offload
Date: Wed, 3 May 2023 18:27:08 -0700 [thread overview]
Message-ID: <20230503182708.70f479d9@kernel.org> (raw)
In-Reply-To: <ccfccde0-9753-1e54-75b0-f6f1d683d765@amd.com>
On Wed, 3 May 2023 15:49:27 -0700 Shannon Nelson wrote:
> Given that there is no traffic to the host PF in this case, and I can't
> do anything more than wave my hands at vague promises for the future,
> perhaps tc and representors is the wrong path for now.
If it's not a priority for AMD to have an upstream implementation
that's fine. There's not point over-complicating the discussion.
> But there remains a need for some port related configuration. I can
> take a stab at adding this concept to "devlink port function" and see
> what discussion follows from there.
You mean setting vlan encap via devlink?
I don't know why you'd do that. It will certainly aggravate me,
and I doubt anyone will care/support you.
next prev parent reply other threads:[~2023-05-04 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 16:45 [PATCH RFC net-next 0/2] pds_core: add switchdev and tc for vlan offload Shannon Nelson
2023-04-27 16:45 ` [PATCH RFC net-next 1/2] pds_core: netdev representors for each VF Shannon Nelson
2023-04-27 16:45 ` [PATCH RFC net-next 2/2] pds_core: tc command handling for vlan push-pop Shannon Nelson
2023-04-28 22:52 ` [PATCH RFC net-next 0/2] pds_core: add switchdev and tc for vlan offload Samudrala, Sridhar
2023-05-02 20:59 ` Shannon Nelson
2023-05-02 23:43 ` Jakub Kicinski
2023-05-03 22:49 ` Shannon Nelson
2023-05-04 1:27 ` Jakub Kicinski [this message]
2023-05-04 20:51 ` Shannon Nelson
2023-05-04 21:14 ` Jakub Kicinski
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=20230503182708.70f479d9@kernel.org \
--to=kuba@kernel.org \
--cc=brett.creeley@amd.com \
--cc=drivers@pensando.io \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.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).