netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gregory.v.rose@intel.com
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] rtnetlink: Add filter for VF info dump requests
Date: Wed, 08 Feb 2012 20:10:18 -0500 (EST)	[thread overview]
Message-ID: <20120208.201018.97784090083485473.davem@davemloft.net> (raw)
In-Reply-To: <20120207223346.21320.89370.stgit@gitlad.jf.intel.com>

From: Greg Rose <gregory.v.rose@intel.com>
Date: Tue, 07 Feb 2012 14:33:46 -0800

> Add a 256 bit filter to allow the user to filter which VFs' info will
> get displayed during the dump info request.  This is to fix a bug in
> which a an info dump request on a device with many VFs would overflow
> the recvmsg buffer which is allocated to max(8192, PAGE_SIZE).  A
> complimentary patch to the iproute2 ip tool will allow the user to
> set/clear individual VF filters.
> 
> Signed-off-by: Greg Rose <gregory.v.rose@intel.com>

This isn't the idea.

I meant we have to add a generic u32 mask attribute to the GETLINK
requests, and it's a mask of "features".  One feature bit would be for
enabling the "VF" part of the dump, another bit would be for the
macvlan source address lists that are being proposed, etc.  Any new
auxiliarry information type we want to add to devide dumps, we have
to add a feature bit for in this mask.

And then you can't just stop there, you have to update all of the
logic related to min_ifinfo_dump_size to take into account the current
request's mask state.

In fact this means you must get rid of the min_info_dump_size global
variable altogether because the size is context dependent upon the
mask configuration of the current dump request.

  reply	other threads:[~2012-02-09  1:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 22:33 [RFC PATCH] rtnetlink: Add filter for VF info dump requests Greg Rose
2012-02-09  1:10 ` David Miller [this message]
2012-02-09 16:25   ` Rose, Gregory V
2012-02-09 18:43     ` David Miller
2012-02-09 18:45       ` Rose, Gregory V
2012-02-09 18:49         ` David Miller
2012-02-09 18:57           ` Rose, Gregory V
2012-02-09 19:01             ` David Miller
2012-02-09 19:06               ` Rose, Gregory V
2012-02-09 19:11                 ` Stephen Hemminger
2012-02-09 19:13                   ` Rose, Gregory V
2012-02-09 19:17                 ` David Miller

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=20120208.201018.97784090083485473.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gregory.v.rose@intel.com \
    --cc=netdev@vger.kernel.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).