Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Falcon <tlfalcon@linux.ibm.com>
To: Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, jiri@nvidia.com
Subject: Re: Exposing device ACL setting through devlink
Date: Tue, 8 Sep 2020 13:27:13 -0500 [thread overview]
Message-ID: <7e4c2c8f-a5b0-799c-3083-cfefcf37bf10@linux.ibm.com> (raw)
In-Reply-To: <20200904153751.17ad4b48@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 9/4/20 5:37 PM, Jakub Kicinski wrote:
> On Fri, 4 Sep 2020 10:31:41 +0200 Jiri Pirko wrote:
>> Thu, Sep 03, 2020 at 07:59:45PM CEST, tlfalcon@linux.ibm.com wrote:
>>> Hello, I am trying to expose MAC/VLAN ACL and pvid settings for IBM
>>> VNIC devices to administrators through devlink (originally through
>>> sysfs files, but that was rejected in favor of devlink). Could you
>>> give any tips on how you might go about doing this?
>> Tom, I believe you need to provide more info about what exactly do you
>> need to setup. But from what you wrote, it seems like you are looking
>> for bridge/tc offload. The infra is already in place and drivers are
>> implementing it. See mlxsw for example.
> I think Tom's use case is effectively exposing the the VF which VLANs
> and what MAC addrs it can use. Plus it's pvid. See:
>
> https://www.spinics.net/lists/netdev/msg679750.html
Thanks, Jakub,
Right now, the use-case is to expose the allowed VLAN's and MAC
addresses and the VF's PVID. Other use-cases may be explored later on
though.
next prev parent reply other threads:[~2020-09-08 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 17:59 Thomas Falcon
2020-09-04 8:31 ` Jiri Pirko
2020-09-04 22:37 ` Jakub Kicinski
2020-09-08 18:27 ` Thomas Falcon [this message]
2020-09-10 7:00 ` Jiri Pirko
2020-09-17 20:31 ` Thomas Falcon
2020-09-18 7:20 ` Jiri Pirko
2020-09-18 23:20 ` Thomas Falcon
2020-09-20 15:21 ` Jiri Pirko
2020-09-21 17:51 ` Thomas Falcon
2020-09-21 20:37 ` Jakub Kicinski
2020-09-23 17:01 ` Thomas Falcon
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=7e4c2c8f-a5b0-799c-3083-cfefcf37bf10@linux.ibm.com \
--to=tlfalcon@linux.ibm.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--subject='Re: Exposing device ACL setting through devlink' \
/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
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).