From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 0AEC98D4D for ; Mon, 21 Sep 2015 16:41:32 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP; 21 Sep 2015 07:41:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,568,1437462000"; d="scan'208";a="809845442" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by fmsmga002.fm.intel.com with ESMTP; 21 Sep 2015 07:41:31 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.252]) by IRSMSX152.ger.corp.intel.com ([169.254.6.126]) with mapi id 14.03.0248.002; Mon, 21 Sep 2015 15:41:30 +0100 From: "Ananyev, Konstantin" To: "Serguei Bezverkhi (sbezverk)" , "Van Haaren, Harry" , "dev@dpdk.org" Thread-Topic: getting pointer for struct ixgbe_hw Thread-Index: AdD0dZo794ndB0TST96I2nQYx9ybgAAAJkCgAAAuJRAAAOXp4A== Date: Mon, 21 Sep 2015 14:41:29 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725836A99BD1@irsmsx105.ger.corp.intel.com> References: 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] getting pointer for struct ixgbe_hw 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: Mon, 21 Sep 2015 14:41:33 -0000 Hi Serguei, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Serguei Bezverkhi (s= bezverk) > Sent: Monday, September 21, 2015 3:12 PM > To: Van Haaren, Harry; dev@dpdk.org > Subject: Re: [dpdk-dev] getting pointer for struct ixgbe_hw >=20 > Hi Harry, >=20 > Thank you for your reply. The reason I was looking for specifically ixgb= e_hw because I needed access to ixgbe PF/VF mailbox facility. I > am not sure if it is exposed via rte_eth api. Please advise. You are not supposed to send/recv messages via HW mailbox directly from the= user application. To configure device there exists rte_eth* API.=20 Wonder what exactly you are trying to achieve? Konstantin >=20 > Best regards >=20 > Serguei >=20 >=20 > Serguei Bezverkhi, > TECHNICAL LEADER.SERVICES > Global SP Services > sbezverk@cisco.com > Phone:=A0+1 416 306 7312 > Mobile:=A0+1 514 234 7374 >=20 > CCIE (R&S,SP,Sec) - #9527 >=20 > Cisco.com >=20 >=20 >=20 > =A0Think before you print. > This email may contain confidential and privileged material for the sole = use of the intended recipient. Any review, use, distribution or > disclosure by others is strictly prohibited. If you are not the intended = recipient (or authorized to receive for the recipient), please > contact the sender by reply email and delete all copies of this message. > Please=A0click here=A0for Company Registration Information. >=20 >=20 >=20 > -----Original Message----- > From: Van Haaren, Harry [mailto:harry.van.haaren@intel.com] > Sent: Monday, September 21, 2015 10:06 AM > To: Serguei Bezverkhi (sbezverk) ; dev@dpdk.org > Subject: RE: getting pointer for struct ixgbe_hw >=20 > Hi Serguei, >=20 > > From: Serguei Bezverkhi > > I would appreciate if somebody could share an example of getting > > access to ixgbe_hw structure for already initialized ixgbe nic. I > > tried to find any references but could not find any API returning point= er for this structure. >=20 > The ixgbe_hw struct is part of the implementation, and should not be used= by code outside the drivers/net/ixgbe director. The > rte_eth_* api[1] is available to access any NIC using a unified API. >=20 > Hope that helps, -Harry >=20 > [1] http://www.dpdk.org/doc/api/rte__ethdev_8h.html