All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@voltaire.com>
To: Simon Horman <horms@verge.net.au>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	Alexander Duyck <alexander.duyck@gmail.com>
Subject: Re: igb bandwidth allocation configuration
Date: Tue, 15 Sep 2009 16:27:25 +0300	[thread overview]
Message-ID: <4AAF963D.4060708@voltaire.com> (raw)
In-Reply-To: <20090915113659.GJ24194@verge.net.au>

Simon Horman wrote:
> It seems to me that the main problem is that from a driver point of view the PF and VFs are independent. But from a hardware point of view they aren't so its not always possible for their configuration to be independent of each other. And I'm not sure what (existing) interfaces can handle that nicely.

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.

> Its not clear to me what you are asking.
I'm was asking/wondering if the Intel NICs have a rate limiter (i.e one 
can program the VF such that its rate doesn't exceed XX MB/s) or a "rate 
guarantee"  (i.e one can program the VF such that its guaranteed it will 
get YY MB/s in case it wants to xmit at least this bandwidth)

Or.


------------------------------------------------------------------------------
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

  reply	other threads:[~2009-09-15 13:27 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 [this message]
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
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=4AAF963D.4060708@voltaire.com \
    --to=ogerlitz@voltaire.com \
    --cc=alexander.duyck@gmail.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=horms@verge.net.au \
    --cc=jeffrey.t.kirsher@intel.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 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.