From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 3CC5A595A for ; Tue, 4 Mar 2014 16:33:50 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 04 Mar 2014 07:35:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,585,1389772800"; d="scan'208";a="493876032" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by orsmga002.jf.intel.com with ESMTP; 04 Mar 2014 07:35:16 -0800 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.62]) by IRSMSX102.ger.corp.intel.com ([169.254.2.180]) with mapi id 14.03.0123.003; Tue, 4 Mar 2014 15:33:34 +0000 From: "Ananyev, Konstantin" To: Sharath Thread-Topic: [dpdk-dev] are these bypass api supported on Intel Bandon Beach card : of device id : 8086:155d Thread-Index: AQHPNUKQE1obbar7+0qEFz9gmrfTgZrO5NKAgABE9ACAAVbPAIAAkWhA Date: Tue, 4 Mar 2014 15:33:33 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725808E7E8C4@IRSMSX105.ger.corp.intel.com> References: <2601191342CEEE43887BDE71AB97725808E7A34D@IRSMSX105.ger.corp.intel.com> In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] are these bypass api supported on Intel Bandon Beach card : of device id : 8086:155d X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2014 15:33:50 -0000 Hi Sharath, About restrictions: the only one I can remember is that bypass API works on= ly on port 0 of the NIC. =20 For port 1 all bypass API functions would just fail. About your particular problem - I wonder can you reproduce it with testpmd? If yes, what particular commands did you use? Thanks Konstantin From: Sharath [mailto:sharathjm.bharadwaj@gmail.com]=20 Sent: Tuesday, March 04, 2014 6:47 AM To: Ananyev, Konstantin Cc: dev@dpdk.org Subject: Re: [dpdk-dev] are these bypass api supported on Intel Bandon Beac= h card : of device id : 8086:155d Thanks for the response Konstantin. The macro is enabled in my setup. The problem which I am facing now is, if I give time interval between the b= ypass and normal state. it is not working assume in the first run I will put the NIC into bypass=20 then leave for 5 min later, in second run if I make the NIC into norm state using the same set o= f API, the NIC is not coming to norm state. the link state is showing as down. Is there any restriction/any other setting required to work with these api;= s/ thanks, Sharath On Mon, Mar 3, 2014 at 3:54 PM, Ananyev, Konstantin wrote: Hi, Yes Bandon Beach should be supported starting from 1.5.1. Though to enable it you need to set CONFIG_RTE_NIC_BYPASS=3Dy in your confi= g file. Konstantin -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sharath Sent: Monday, March 03, 2014 6:13 AM To: dev@dpdk.org Subject: Re: [dpdk-dev] are these bypass api supported on Intel Bandon Beac= h card : of device id : 8086:155d can anyone please let me know about this... thanks, Sharath On Sat, Mar 1, 2014 at 5:06 PM, Sharath wrot= e: > Hi > > we are using DPDK 1.5.1_7. > our PCI slot has Intel Bandon Beach NIC. > > > Can anyone please let me know, whether the below api's are supported > in the NIC type [8086:155d] > > int rte_eth_dev_bypass_init (uint8_t port) > > * int rte_eth_dev_bypass_state_show (uint8_t port, uint32_t _state) > > * int rte_eth_dev_bypass_state_set (uint8_t port, uint32_t _new_state) > > * int rte_eth_dev_bypass_event_show (uint8_t port, uint32_t event, > uint32_t _state) > > * int rte_eth_dev_bypass_event_store (uint8_t port, uint32_t event, > uint32_t state) > > * int rte_eth_dev_bypass_ver_show (uint8_t port, uint32_t _ver) > > * int rte_eth_dev_bypass_wd_timeout_show (uint8_t port, > > > thanks > Sharath >