From: Jakub Kicinski <kuba@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
Gal Pressman <gal@nvidia.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"David S. Miller" <davem@davemloft.net>,
Michal Kubecek <mkubecek@suse.cz>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Edwin Peer <espeer@gmail.com>
Subject: Re: [PATCH net-next] rtnetlink: extend RTEXT_FILTER_SKIP_STATS to IFLA_VF_INFO
Date: Wed, 14 Jun 2023 09:39:52 -0700 [thread overview]
Message-ID: <20230614093952.6e1eadc8@kernel.org> (raw)
In-Reply-To: <15de5df0-9a29-d592-0ac8-e2c470b17c83@gmail.com>
On Wed, 14 Jun 2023 08:17:44 -0700 David Ahern wrote:
> > As it looks like the is substantial agreement on this approach being a
> > step in the right direction and I can't think of anything better, I
> > suggest to merge this as is, unless someone voices concerns very soon,
> > very loudly.
>
> My only concern is that this "hot potato" stays in the air longer. This
> problem has been around for years, and someone needs to step up and
> propose an API.
The functionality is fully covered by devlink and tc. We're not
accepting any new drivers/implementations of the old SR-IOV NDOs
at all.
We try to put this potato in the grave and it keeps trying to grow :(
next prev parent reply other threads:[~2023-06-14 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 10:51 [PATCH net-next] rtnetlink: extend RTEXT_FILTER_SKIP_STATS to IFLA_VF_INFO Gal Pressman
2023-06-11 15:06 ` Stephen Hemminger
2023-06-11 17:58 ` Gal Pressman
2023-06-12 5:34 ` Keller, Jacob E
2023-06-14 9:03 ` Paolo Abeni
2023-06-14 15:17 ` David Ahern
2023-06-14 16:39 ` Jakub Kicinski [this message]
2023-06-14 13:20 ` patchwork-bot+netdevbpf
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=20230614093952.6e1eadc8@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=espeer@gmail.com \
--cc=gal@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).