[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43F901BD926A4E43B106BF17856F0755014603C6BE@orsmsx508.amr.corp.intel.com>
Date: Fri, 22 Apr 2011 15:29:41 -0700
From: "Rose, Gregory V" <gregory.v.rose@...el.com>
To: Ben Hutchings <bhutchings@...arflare.com>
CC: David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
sf-linux-drivers <linux-net-drivers@...arflare.com>
Subject: RE: rtnetlink and many VFs
> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
> On Behalf Of Ben Hutchings
> Sent: Thursday, April 21, 2011 11:12 AM
> To: Rose, Gregory V
> Cc: David Miller; netdev; sf-linux-drivers
> Subject: RE: rtnetlink and many VFs
>
> > > I think that what 'ip link show' is doing now seems to be perfectly
> > > valid. It allocates a 16K buffer which would be enough if netlink
> > > didn't apply this PAGE_SIZE limit to single messages.
> >
If someone who knew (or knows) a bit more about netlink could point out where this limitation is set in the code I'd really appreciate it. I've been poking around for a few hours and still can't find it. I found the spot in the iproute2 code where the 16k is allocated and traced it down to the netlink socket call but from the kernel side I just can't find this PAGE_SIZE limit invocation.
- Greg
Powered by blists - more mailing lists