From: Patrick McHardy <kaber@trash.net>
To: Yu Zhao <yu.zhao@intel.com>
Cc: "shemminger@vyatta.com" <shemminger@vyatta.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
David Miller <davem@davemloft.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gospo@redhat.com" <gospo@redhat.com>
Subject: Re: [net-next PATCH v3] igbvf: add new driver to support 82576 virtual functions
Date: Thu, 26 Mar 2009 14:05:07 +0100 [thread overview]
Message-ID: <49CB7D83.10205@trash.net> (raw)
In-Reply-To: <20090326023343.GA8138@yzhao-otc.sh.intel.com>
Yu Zhao wrote:
> We do have some powerful tools for network device configuration, but they
> still can't cover the multi queue and SR-IOV NICs (also David Woodhouse's
> Solos DSL, etc.) configuration requirement. Unless someone improves the
> existing tools to support configuring these new hardware features, people
> would keep trying to use the sysfs which is the easiest way so far.
So what are these missing features in the existing interfaces?
next prev parent reply other threads:[~2009-03-26 13:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 21:52 [net-next PATCH v3] igbvf: add new driver to support 82576 virtual functions Jeff Kirsher
2009-03-25 22:00 ` Jeff Kirsher
2009-03-25 22:03 ` Stephen Hemminger
2009-03-25 22:33 ` Alexander Duyck
2009-03-25 23:58 ` David Miller
2009-03-26 0:54 ` Alexander Duyck
2009-03-26 2:33 ` Yu Zhao
2009-03-26 3:16 ` David Miller
2009-03-26 13:05 ` Patrick McHardy [this message]
2009-03-26 3:12 ` David Miller
2009-03-26 3:21 ` Roland Dreier
2009-03-26 3:33 ` David Miller
2009-03-26 3:27 ` Alexander Duyck
2009-03-26 3:34 ` David Miller
2009-03-27 0:30 ` [ RFC ] igb: first draft of igb rtnl_link_ops interface for vf creation (was Re: [net-next PATCH v3] igbvf: add new driver to support 82576 virtual functions) Alexander Duyck
2009-03-27 5:35 ` Patrick McHardy
2009-03-27 15:22 ` [ RFC ] igb: first draft of igb rtnl_link_ops interface for vf creation 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=49CB7D83.10205@trash.net \
--to=kaber@trash.net \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=yu.zhao@intel.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.