From: Eric Dumazet <eric.dumazet@gmail.com>
To: Steve Hodgson <shodgson@solarflare.com>
Cc: "Rose, Gregory V" <gregory.v.rose@intel.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bhutchings@solarflare.com" <bhutchings@solarflare.com>
Subject: Re: [RFC PATCH] netlink: Increase netlink dump skb message size
Date: Wed, 27 Apr 2011 18:30:09 +0200 [thread overview]
Message-ID: <1303921809.3166.90.camel@edumazet-laptop> (raw)
In-Reply-To: <4DB83A60.5040102@solarflare.com>
Le mercredi 27 avril 2011 à 16:46 +0100, Steve Hodgson a écrit :
> On 04/27/2011 04:24 PM, Eric Dumazet wrote:
> > Le mardi 26 avril 2011 à 09:12 -0700, Rose, Gregory V a écrit :
> >
> >> I'm fine with however you folks want to approach this, just give me some direction.
> >
> > I would just try following patch :
> >
>
> This allows the sfc driver to use 102 VFs, up from the current limit of
> 45 VFs.
>
> It's unfortunate that this patch isn't sufficient to allow all 127 VFs
> to be used, but whilst we wait for a new netlink api this is an
> improvement worth having.
>
netlink recvmsg() supports MSG_PEEK so user would get the needed size of
its buffer before calling the real recvmsg()
big blobs could be attached as skb fragments (up to 64Kbytes), but do we
really want this...
next prev parent reply other threads:[~2011-04-27 16:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 22:01 [RFC PATCH] netlink: Increase netlink dump skb message size Greg Rose
2011-04-26 6:33 ` Eric Dumazet
2011-04-26 6:56 ` David Miller
2011-04-26 16:12 ` Rose, Gregory V
2011-04-26 16:21 ` Eric Dumazet
2011-04-26 16:24 ` Rose, Gregory V
2011-04-26 19:07 ` Ben Hutchings
2011-04-26 21:58 ` Rose, Gregory V
2011-04-27 15:46 ` Steve Hodgson
2011-04-27 16:30 ` Eric Dumazet [this message]
2011-04-27 17:15 ` Rose, Gregory V
2011-04-27 17:29 ` Eric Dumazet
2011-04-27 17:39 ` Rose, Gregory V
2011-04-27 18:05 ` Eric Dumazet
2011-04-27 18:08 ` Rose, Gregory V
2011-04-26 16:02 ` Rose, Gregory V
2011-04-29 19:29 ` David Miller
2011-04-29 19:37 ` Rose, Gregory V
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=1303921809.3166.90.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shodgson@solarflare.com \
/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