netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>,
	Gal Pressman <gal@nvidia.com>,
	 Stephen Hemminger <stephen@networkplumber.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	 David Ahern <dsahern@gmail.com>,
	Michal Kubecek <mkubecek@suse.cz>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Edwin Peer <edwin.peer@broadcom.com>,
	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 11:03:17 +0200	[thread overview]
Message-ID: <a9d5cf824500c3a4d86f26bd18ec29b6dfd2daf8.camel@redhat.com> (raw)
In-Reply-To: <CO1PR11MB50899E098BB3FFE0DE322222D654A@CO1PR11MB5089.namprd11.prod.outlook.com>

On Mon, 2023-06-12 at 05:34 +0000, Keller, Jacob E wrote:
> > -----Original Message-----
> > From: Gal Pressman <gal@nvidia.com>
> > Sent: Sunday, June 11, 2023 10:59 AM
> > To: Stephen Hemminger <stephen@networkplumber.org>
> > Cc: David S. Miller <davem@davemloft.net>; Jakub Kicinski <kuba@kernel.org>;
> > David Ahern <dsahern@gmail.com>; Michal Kubecek <mkubecek@suse.cz>;
> > netdev@vger.kernel.org; Edwin Peer <edwin.peer@broadcom.com>; Edwin Peer
> > <espeer@gmail.com>
> > Subject: Re: [PATCH net-next] rtnetlink: extend RTEXT_FILTER_SKIP_STATS to
> > IFLA_VF_INFO
> > 
> > On 11/06/2023 18:06, Stephen Hemminger wrote:
> > 
> > > Better but it is still possible to create too many VF's that the response
> > > won't fit.
> > 
> > Correct, no argues here.
> > It allowed me to see around ~200 VFs instead of ~70, a step in the right
> > direction.
> 
> I remember investigating this a few years ago and we hit limits of ~200 that were essentially unfixable without creating a new API that can separate the reply over more than one message. The VF info data was not designed in the current op to allow processing over multiple messages. It also (unfortunately) doesn't report errors so it ends up just truncating instead of producing an error.
> 
> Fixing this completely is non-trivial.

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.

Thanks!

Paolo


  reply	other threads:[~2023-06-14  9:03 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 [this message]
2023-06-14 15:17         ` David Ahern
2023-06-14 16:39           ` Jakub Kicinski
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=a9d5cf824500c3a4d86f26bd18ec29b6dfd2daf8.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edwin.peer@broadcom.com \
    --cc=espeer@gmail.com \
    --cc=gal@nvidia.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --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).