[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DD92D5A8-1ECC-4440-BE81-ABDCC6847021@qlogic.com>
Date: Thu, 22 Apr 2010 22:57:51 -0700
From: Anirban Chakraborty <anirban.chakraborty@...gic.com>
To: Scott Feldman <scofeldm@...co.com>
CC: David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"chrisw@...hat.com" <chrisw@...hat.com>,
Arnd Bergmann <arnd@...db.de>,
Ameen Rahman <ameen.rahman@...gic.com>,
Amit Salecha <amit.salecha@...gic.com>,
Rajesh Borundia <rajesh.borundia@...gic.com>
Subject: Re: eSwitch management
On Apr 22, 2010, at 6:29 PM, Scott Feldman wrote:
> On 4/22/10 5:47 PM, "Scott Feldman" <scofeldm@...co.com> wrote:
>
>> On 4/22/10 4:16 PM, "Anirban Chakraborty" <anirban.chakraborty@...gic.com>
>> wrote:
>>
>>> I am following the discussions on iovnl patch closely. While it is going to
>>> take some time for iovnl patch to be reviewed and accepted, what would be the
>>> interim approach to manage the eswitch in NIC? We need to add support in
>>> qlcnic driver to configure the eswitch in our 10G NIC. Some of the things
>>> that
>>> we need to set to the switch are setting a port's VLAN, tx bandwidth etc. We
>>> would like to set these parameters for a bunch of ports at the start of the
>>> day and set it to the eswitch.
>>
>> Are any of these settings covered in DCB? (net/dcb/dcbnl.c). Maybe you can
>> get a start there? Not sure not knowing your device requirements.
>
> Or maybe the RTM_SETLINK IFLA_VF_* ops in include/linux/if_link.h? Those
> seem like what you're looking for. I'm looking at moving iovnl here as well
> for port-profile.
It looks like ifla_vf_info does contain most of the data set. But if I use it, what NETLINK protocol family should I use in my driver to receive netlink messages? Do I need to create a private protocol family?
Thanks a lot,
Anirban
--
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