From: Or Gerlitz <or.gerlitz@gmail.com>
To: Simon Horman <horms@verge.net.au>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Alexander Duyck <alexander.duyck@gmail.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
Or Gerlitz <ogerlitz@voltaire.com>
Subject: Re: igb bandwidth allocation configuration
Date: Mon, 14 Sep 2009 11:42:50 +0300 [thread overview]
Message-ID: <15ddcffd0909140142n2a110708ld619177c65f4588b@mail.gmail.com> (raw)
In-Reply-To: <20090910081844.GA5421@verge.net.au>
On 9/10/09, Simon Horman <horms@verge.net.au> wrote:
> I have been looking into adding support the 82586's per-PF/VF bandwidth allocation to
> the igb driver. It seems that the trickiest part is working out how to expose things to
> user-space.
Please note that there are bunch (not many, but more then 1-2) of
things to configure from user space in a PF/VF scheme, and I think it
would be best if we do that through one mechanism, which may be
netlink based or extension to ethtool as you suggested, we've started
to discuss this on the "L2 switching in igb" thread
The "82576 SR-IOV Driver Companion Guide" document, section 7.6
mentions "Transmit Bandwidth Allocation to VFs... define minimum
transmit bandwidth for individual VMs".
I'm not clear if one can program rate limiter (upper bound) per VF or
actually rate guarantee per VF, even with these being just details
of specific device, alex, I would be happy if you can clarify that.
Or.
next prev parent reply other threads:[~2009-09-14 8:42 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 [this message]
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
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=15ddcffd0909140142n2a110708ld619177c65f4588b@mail.gmail.com \
--to=or.gerlitz@gmail.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 \
--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 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).