From: Jakub Kicinski <kuba@kernel.org>
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: ecree@xilinx.com, davem@davemloft.net, pabeni@redhat.com,
linux-net-drivers@amd.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 12/14] sfc: set EF100 VF MAC address through representor
Date: Thu, 28 Jul 2022 18:45:27 -0700 [thread overview]
Message-ID: <20220728184527.3f3dd520@kernel.org> (raw)
In-Reply-To: <5a4d22f2-e315-b6f4-5fb5-31134960c430@gmail.com>
On Thu, 28 Jul 2022 21:23:23 +0100 Edward Cree wrote:
> Sadly I was too busy with EF100 bring-up, and naïvely assumed that I
> could safely ignore devlink port stuff as it was so obviously going
> to be a classic Mellanox design: tasteless, overweight, and not
> cleanly mappable onto any other vendor. Which seems to have been
> true but they've managed to make it the standard anyway by virtue
> of being there first, as usual :'(
> (Yeah, I probably shouldn't publicly say things like that about
> another vendor's devs. But I'm getting frustrated at this recurring
> pattern.)
I spend an unhealthy amount of time thinking about the problem
of vendors not paying attention when new uAPIs are forged.
Happy to try things.
> Devlink port function *would* be useful for administering functions
> that don't have a representor. I just can't see any good reason
> why such things should ever exist.
The SmartNIC/DPU/IPU/isolated hv+IO CPU can expose storage functions
to the peer. nVidia is working on extending the devlink rate limit API
to cover such cases.
next prev parent reply other threads:[~2022-07-29 1:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 17:45 [PATCH net-next v2 00/14] sfc: VF representors for EF100 - RX side ecree
2022-07-27 17:45 ` [PATCH net-next v2 01/14] sfc: plumb ef100 representor stats ecree
2022-07-27 17:45 ` [PATCH net-next v2 02/14] sfc: ef100 representor RX NAPI poll ecree
2022-07-27 17:45 ` [PATCH net-next v2 03/14] sfc: ef100 representor RX top half ecree
2022-07-27 17:45 ` [PATCH net-next v2 04/14] sfc: determine wire m-port at EF100 PF probe time ecree
2022-07-27 17:45 ` [PATCH net-next v2 05/14] sfc: check ef100 RX packets are from the wire ecree
2022-07-27 17:45 ` [PATCH net-next v2 06/14] sfc: receive packets from EF100 VFs into representors ecree
2022-07-27 17:45 ` [PATCH net-next v2 07/14] sfc: insert default MAE rules to connect VFs to representors ecree
2022-07-27 17:45 ` [PATCH net-next v2 08/14] sfc: move table locking into filter_table_{probe,remove} methods ecree
2022-07-27 17:45 ` [PATCH net-next v2 09/14] sfc: use a dynamic m-port for representor RX and set it promisc ecree
2022-07-27 17:46 ` [PATCH net-next v2 10/14] sfc: look up VF's client ID when creating representor ecree
2022-07-27 17:46 ` [PATCH net-next v2 11/14] sfc: fetch existing assigned MAC address from FW when creating VF rep ecree
2022-07-27 17:46 ` [PATCH net-next v2 12/14] sfc: set EF100 VF MAC address through representor ecree
2022-07-28 3:10 ` Jakub Kicinski
2022-07-28 15:47 ` Edward Cree
2022-07-28 16:20 ` Jakub Kicinski
2022-07-28 18:12 ` Edward Cree
2022-07-28 18:32 ` Jakub Kicinski
2022-07-28 18:54 ` Edward Cree
2022-07-28 19:27 ` Jakub Kicinski
2022-07-28 20:23 ` Edward Cree
2022-07-29 1:45 ` Jakub Kicinski [this message]
2022-07-29 15:17 ` Edward Cree
2022-07-27 17:46 ` [PATCH net-next v2 13/14] sfc: get provisioned MAC address on EF100 VF probe ecree
2022-07-27 17:46 ` [PATCH net-next v2 14/14] sfc: implement ethtool get/set RX ring size for EF100 reps ecree
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=20220728184527.3f3dd520@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=ecree@xilinx.com \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).