From: David Miller <davem@davemloft.net>
To: gregory.v.rose@intel.com
Cc: bhutchings@solarflare.com, netdev@vger.kernel.org,
linux-net-drivers@solarflare.com
Subject: Re: rtnetlink and many VFs
Date: Fri, 22 Apr 2011 15:31:45 -0700 (PDT) [thread overview]
Message-ID: <20110422.153145.183062300.davem@davemloft.net> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F0755014603C6BE@orsmsx508.amr.corp.intel.com>
From: "Rose, Gregory V" <gregory.v.rose@intel.com>
Date: Fri, 22 Apr 2011 15:29:41 -0700
> 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.
NLMSG_GOODSIZE
next prev parent reply other threads:[~2011-04-22 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 14:36 rtnetlink and many VFs Ben Hutchings
2011-04-21 17:02 ` Rose, Gregory V
2011-04-21 17:40 ` Ben Hutchings
2011-04-21 17:50 ` Rose, Gregory V
2011-04-21 18:11 ` Ben Hutchings
2011-04-21 18:28 ` Rose, Gregory V
2011-04-22 22:29 ` Rose, Gregory V
2011-04-22 22:31 ` David Miller [this message]
2011-04-22 22:49 ` 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=20110422.153145.183062300.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=gregory.v.rose@intel.com \
--cc=linux-net-drivers@solarflare.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