[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C5551D9AAB213A418B7FD5E4A6F30A0702F8759A@ORSMSX106.amr.corp.intel.com>
Date: Thu, 9 Feb 2012 19:06:02 +0000
From: "Rose, Gregory V" <gregory.v.rose@...el.com>
To: David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [RFC PATCH] rtnetlink: Add filter for VF info dump requests
> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
> On Behalf Of David Miller
> Sent: Thursday, February 09, 2012 11:02 AM
> To: Rose, Gregory V
> Cc: netdev@...r.kernel.org
> Subject: Re: [RFC PATCH] rtnetlink: Add filter for VF info dump requests
>
> From: "Rose, Gregory V" <gregory.v.rose@...el.com>
> Date: Thu, 9 Feb 2012 18:57:26 +0000
>
> > I'm sure the consternation on my part is that I had thought you
> > wanted the feature bits to default to none. You said this at one
> > point:
>
> In "the kernel", so that things like GLIBC, that don't ask for the
> features, no longer break with lots of VFs.
>
> "iproute2" in userland can set all the feature bits, and have code
> added to accomodate large dump requests in the future, so you're going
> to have to make changes to iproute2 for this.
OK, that's a bit more clear to me then. And that's the only reason I mentioned that the semantics to 'ip link show' would change. But now I see what you mean by the rubbish comment. By default ip link show will set all the feature bits and I'll add option code to iproute2 to allow the user to turn it off.
Does that make sense?
- Greg
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists