All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Alexander Duyck <alexander.h.duyck@intel.com>
Cc: Or Gerlitz <ogerlitz@voltaire.com>,
	"e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	Alexander Duyck <alexander.duyck@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: igb bandwidth allocation configuration
Date: Thu, 17 Sep 2009 11:09:35 +1000	[thread overview]
Message-ID: <20090917010935.GA19201@verge.net.au> (raw)
In-Reply-To: <20090915222926.GA24467@verge.net.au>

On Wed, Sep 16, 2009 at 08:29:26AM +1000, Simon Horman wrote:
> On Tue, Sep 15, 2009 at 11:01:52AM -0700, Alexander Duyck wrote:
> > Or Gerlitz wrote:
> > >If the rate limiter is exposed as a feature of the VF, it doesn't
> > >matter who really enforces it, the "VF portion" of the HW or the
> > >PF itself. I agree that if you have to program the PF for the rate
> > >of a specific VF, then its more complex. Basically, I would expect
> > >that a VF can be configured with <mac, vlad-id, priority, rate>
> > >such that it can be done where the VF NIC is spawned, host kernel
> > >or guest kernel.
> > 
> > Adding the rate limiter as a feature of the VF doesn't make much
> > sense since the VF could be direct assigned to another OS for all we
> > know so we won't have control over it from there.
> > 
> > The interface for all of this would make sense as part of a virtual
> > ethernet switch control which is the way I am currently leaning on
> > all this.  As such it is probably another thing we can bring up at
> > the BOF session at the Linux Plumbers Conference.
> 
> Unfortunately I won't be able to make it to the BOF or Plumbers.
> I look forward to hearing what is discussed.

Is there any chance of being able to participate in this remotely,
even just a listen-only feed of some sort would be quite valuable to me
and possibly others.

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf

  parent reply	other threads:[~2009-09-17  1:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10  8:18 igb bandwidth allocation configuration Simon Horman
2009-09-10 11:28 ` Patrick McHardy
2009-09-10 11:55   ` Patrick McHardy
2009-09-11  0:38     ` Simon Horman
2009-09-15 11:32       ` Simon Horman
2009-09-14  8:42 ` Or Gerlitz
2009-09-15 11:36   ` Simon Horman
2009-09-15 13:27     ` Or Gerlitz
2009-09-15 18:01       ` Alexander Duyck
2009-09-15 18:25         ` Nelson, Shannon
2009-09-15 22:29         ` Simon Horman
2009-09-16  6:47           ` Or Gerlitz
2009-09-16  7:04             ` Simon Horman
2009-09-16 16:10               ` Nelson, Shannon
2009-09-17  1:09           ` Simon Horman [this message]
2009-09-16 14:10         ` Or Gerlitz
2009-09-16 15:53           ` Alexander Duyck

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=20090917010935.GA19201@verge.net.au \
    --to=horms@verge.net.au \
    --cc=alexander.duyck@gmail.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@voltaire.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.