[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C7F4AD4F.2A34D%scofeldm@cisco.com>
Date: Wed, 21 Apr 2010 13:25:35 -0700
From: Scott Feldman <scofeldm@...co.com>
To: Arnd Bergmann <arnd@...db.de>, Chris Wright <chrisw@...hat.com>
CC: <davem@...emloft.net>, <netdev@...r.kernel.org>
Subject: Re: [net-next,1/2] add iovnl netlink support
On 4/21/10 12:39 PM, "Arnd Bergmann" <arnd@...db.de> wrote:
>>> 1. Setting up the slave device
>>> a) create an SR-IOV VF to assign to a guest
>>> b) create a macvtap device to pass to qemu or vhost
>>> c) attach a tap device to a bridge
>>> d) create a macvlan device and put it into a container
>>> e) create a virtual interface for a VMDq adapter
>>
>> OK, but iovnl isn't doing this.
>
> The set_mac_vlan that Scott's patch adds seems to implement 1a), as far
> as I can tell. Interestingly, this is not actually implemented in
> the enic driver in patch 2/2. So if we all agree that this is out of the
> scope of iovnl, let's just remove it from the interface and find another
> way for it (ethtool, iplink, ..., as listed above).
You're right, not needed for enic since mac addr is included with
port-profile push and vlan membership is implied by port-profile. So I put
set_mac_vlan in there basically to elicit feedback.
There really wouldn't be much different between iplink and iovnl since
they're both rtnetlink...seems we should keep IOV-related APIs in one place.
Maybe there are other IOV APIs to add to iovnl in the future like:
vf <- add_vf(pf)
del_vf(pf, vf)
Ethtool doesn't seem the right place for this.
-scott
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists