From: David Miller <davem@davemloft•net>
To: yu.zhao@intel•com
Cc: shemminger@vyatta•com, alexander.h.duyck@intel•com,
jeffrey.t.kirsher@intel•com, netdev@vger•kernel.org,
gospo@redhat•com
Subject: Re: [net-next PATCH v3] igbvf: add new driver to support 82576 virtual functions
Date: Wed, 25 Mar 2009 20:16:35 -0700 (PDT) [thread overview]
Message-ID: <20090325.201635.245115032.davem@davemloft.net> (raw)
In-Reply-To: <20090326023343.GA8138@yzhao-otc.sh.intel.com>
From: Yu Zhao <yu.zhao@intel•com>
Date: Thu, 26 Mar 2009 10:33:43 +0800
> 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.
We have a generic link creation mechanism in rtnl_link so I think
this claim wrt. SR-IOV is false.
Believe it or not, somebody took the time to make a generic mechanism
for things many virtual network device drivers have to do, and
igb/igbvf can use it too.
next prev parent reply other threads:[~2009-03-26 3:16 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 [this message]
2009-03-26 13:05 ` Patrick McHardy
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=20090325.201635.245115032.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=alexander.h.duyck@intel$(echo .)com \
--cc=gospo@redhat$(echo .)com \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
--cc=yu.zhao@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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