[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100419213531.GG5715@x200.localdomain>
Date: Mon, 19 Apr 2010 14:35:31 -0700
From: Chris Wright <chrisw@...hat.com>
To: Scott Feldman <scofeldm@...co.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, chrisw@...hat.com
Subject: Re: [net-next PATCH 0/2] iovnl netlink ops + enic dynamic vnics
* Scott Feldman (scofeldm@...co.com) wrote:
> Patch 1/2 adds new I/O Virtualization netlink ops:
>
> IOV netlink (IOVNL) adds I/O Virtualization control support to a master
> device (MD) netdev interface. The MD (e.g. SR-IOV PF) will set/get
> control settings on behalf of a slave netdevice (e.g. SR-IOV VF). The
> design allows for the case where master and slave are the
> same netdev interface.
>
> The ops currently defined are:
> set_mac_vlan: set mac+vlan on VF
> set_port_profile: set port-profile on VF
> unset_port_profile: unset port-profile on VF
>
> Patch 2/2 adds IOV netlink ops support to enic dynamic vnics:
>
> Add enic iovnl ops to support setting port-profile for dynamic vnics. Enic
> dynamic vnics are just like normal enic eth vnics except dynamic vnics require
> an extra configuration step to assign a port-profile identifier to the
> interface before the interface is useable. Once assigned, link comes up
> on the interface and is ready for I/O. The port-profile is used to configure
> the network port assigned to the interface. The network port configuration
> includes VLAN membership, QoS policies, and port security settings typical
> of a data center network.
Note that while these just enable enic, the framework should be generic
enough for other drivers and can deliver all the way to userspace daemon
for the case of VSI Discovery Protocol.
thanks,
-chris
--
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