netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: "Rose, Gregory V" <gregory.v.rose@intel.com>
Cc: David Miller <davem@davemloft.net>,
	"steweg@ynet.sk" <steweg@ynet.sk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [patch v1, kernel version 3.2.1] rtnetlink workaround around the skb buff size issue
Date: Tue, 7 Feb 2012 18:26:32 +0000	[thread overview]
Message-ID: <1328639192.3549.14.camel@bwh-desktop> (raw)
In-Reply-To: <C5551D9AAB213A418B7FD5E4A6F30A0702F81413@ORSMSX106.amr.corp.intel.com>

On Tue, 2012-02-07 at 00:13 +0000, Rose, Gregory V wrote:
> > -----Original Message-----
> > From: Ben Hutchings [mailto:bhutchings@solarflare.com]
> > Sent: Monday, February 06, 2012 3:51 PM
> > To: Rose, Gregory V
> > Cc: David Miller; steweg@ynet.sk; linux-kernel@vger.kernel.org;
> > netdev@vger.kernel.org
> > Subject: RE: [patch v1, kernel version 3.2.1] rtnetlink workaround around
> > the skb buff size issue
> > 
> > On Mon, 2012-02-06 at 04:41 +0000, Rose, Gregory V wrote:
> > [...]
> > > > This is not how we're going to fix this.  I already stated the desired
> > > > way to fix this, which is to make the existing dump request have a way
> > > > for the requestor to enable extended parts of the device dump.
> > > >
> > > > This is just like netlink diag socket dumps, where the dump request
> > > > specifies what the user wants to see.
> > > >
> > > > In this case we'd add a netlink attribute to the dump request which
> > > > is just a u32 bitmask or similar.
> > > >
> > > > The Intel engineer who added the VF dump support said he would work on
> > > > this fix so why don't you just wait patiently for him to do the work?
> > >
> > > The patch below is what I've got so far.  Right now the bit mask array
> > > is global so if you enable display of VF (n) on one interface it will
> > > enable display of the same VF on other interfaces.  I intend to move
> > > the bit mask array into the net_device structure so we can set the
> > > display mask for each interface independently.
> > 
> > I don't think this can work.  Using an application that requests VF
> > information and uses large buffers (e.g. the updated 'ip') will break
> > another application that doesn't (e.g. current Network Manager), won't
> > it?
> 
> It's my understanding that the problem isn't with the application
> buffer size but with the kernel buffer size, which is limited to a
> page.
[...]

Then it's no wonder you're going about this the wrong way.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

  reply	other threads:[~2012-02-07 18:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5422254.3711328278789768.JavaMail.root@5-MeO-DMT.ynet.sk>
2012-02-03 14:24 ` [patch v1, kernel version 3.2.1] rtnetlink workaround around the skb buff size issue Stefan Gula
2012-02-04  0:29   ` David Miller
2012-02-06  4:41     ` Rose, Gregory V
2012-02-06  8:53       ` Štefan Gula
2012-02-06 15:15         ` David Miller
2012-02-06 16:56           ` Eric Dumazet
2012-02-06 18:52             ` Štefan Gula
2012-02-06 17:29         ` Rose, Gregory V
2012-02-06 18:32           ` Štefan Gula
2012-02-06 18:36             ` Rose, Gregory V
2012-02-06 23:50       ` Ben Hutchings
2012-02-07  0:13         ` Rose, Gregory V
2012-02-07 18:26           ` Ben Hutchings [this message]
2012-02-07 18:32             ` David Miller
2012-02-07 18:59               ` 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=1328639192.3549.14.camel@bwh-desktop \
    --to=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=gregory.v.rose@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=steweg@ynet.sk \
    /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).