From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Feldman Subject: Re: eSwitch management Date: Thu, 22 Apr 2010 17:47:48 -0700 Message-ID: References: <0B579583-F3D8-4C64-A844-34D69C1760D6@qlogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Cc: "netdev@vger.kernel.org" , "chrisw@redhat.com" , Arnd Bergmann , Ameen Rahman , Amit Salecha , Rajesh Borundia To: Anirban Chakraborty , David Miller Return-path: Received: from sj-iport-5.cisco.com ([171.68.10.87]:39196 "EHLO sj-iport-5.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754500Ab0DWAsB (ORCPT ); Thu, 22 Apr 2010 20:48:01 -0400 In-Reply-To: <0B579583-F3D8-4C64-A844-34D69C1760D6@qlogic.com> Sender: netdev-owner@vger.kernel.org List-ID: On 4/22/10 4:16 PM, "Anirban Chakraborty" 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. -scott