From: Andi Kleen <andi@firstfloor.org>
To: Simon Horman <horms@verge.net.au>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Arnd Bergmann <arndbergmann@googlemail.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: [rfc 0/4] igb: bandwidth allocation
Date: Thu, 05 Nov 2009 13:09:44 +0100 [thread overview]
Message-ID: <87bpjh896f.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20091105005847.941190065@vergenet.net> (Simon Horman's message of "Thu, 05 Nov 2009 11:58:47 +1100")
Simon Horman <horms@verge.net.au> writes:
> Hi,
>
> this series of patches exposes the bandwidth allocation
> hardware support of the Intel 82576. It does so through
> a rather hackish sysfs entry. That interface is just intended
> for testing so that the exposed hardware feature can
> be exercised. I would like to find a generic way to expose
> this feature to user-space.
It would be cool if you had a interface that did a software
fallback for NICs that don't support this.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-11-05 12:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 0:58 [rfc 0/4] igb: bandwidth allocation Simon Horman
2009-11-05 0:58 ` [rfc 1/4] igb: Add igb_cleanup_vf() Simon Horman
2009-11-05 0:58 ` [rfc 2/4] igb: Initialise adapter->vfs_allocated_count in igb_init_vf() Simon Horman
2009-11-05 0:58 ` [rfc 3/4] igb: Common error path in igb_init_vfs() Simon Horman
2009-11-05 0:58 ` [rfc 4/4] igb: expose 82576 bandiwidth allocation Simon Horman
2009-11-05 23:00 ` Alexander Duyck
2009-11-05 23:30 ` Simon Horman
2009-11-05 23:42 ` Alexander Duyck
2009-11-06 3:57 ` Simon Horman
2009-11-05 1:46 ` [rfc 0/4] igb: bandwidth allocation Jeff Kirsher
2009-11-05 2:21 ` Simon Horman
2009-11-14 8:01 ` Jeff Kirsher
2009-11-25 6:31 ` Simon Horman
2009-11-05 12:09 ` Andi Kleen [this message]
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=87bpjh896f.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=arndbergmann@googlemail.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 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).