From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by dpdk.org (Postfix) with ESMTP id B80FC11A2 for ; Mon, 21 Sep 2015 16:53:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4857; q=dns/txt; s=iport; t=1442847213; x=1444056813; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=c7DvRNbCpLXwvONDwZ71eqzxLEY62FGBvVA8e6Kbo64=; b=c5Ud/zvX4rflElVKO55FJHZG4NenNBL3Ml8pRr75Cnm4oGBaNEHCOr1v 9uPClcfIg1q+ni8WHQt85hA5b/rKah8Zxj4aibb0o/qMSdstEN5u+9buD YAczyjdNz3bWlrV3ZRIyk3JFWTWdxR2Ob4e7GujCbMxyWdpcqp2NmpnHg o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DyAQC0GABW/5pdJa1aA4MkVGkGvT8BDYF7hXkCgTU4FAEBAQEBAQGBCoQjAQEBAwGBBQICAgEIEQQBAQsdBxsXFAkIAQEEARIIAYgdCA24HZIwAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwSGb4R9hCoPAgEgCxYSBQYMgwaBFAWNNoguAYUQh3iBS0aDb4cjgVeIMYNtHwEBQoQBcQGIJAIFAhcjgQUBAQE X-IronPort-AV: E=Sophos;i="5.17,568,1437436800"; d="scan'208";a="190049766" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-6.cisco.com with ESMTP; 21 Sep 2015 14:53:31 +0000 Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t8LErURq029030 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 21 Sep 2015 14:53:30 GMT Received: from xch-aln-012.cisco.com (173.36.7.22) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 21 Sep 2015 09:53:29 -0500 Received: from xhc-aln-x12.cisco.com (173.36.12.86) by xch-aln-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Mon, 21 Sep 2015 09:53:29 -0500 Received: from xmb-rcd-x06.cisco.com ([169.254.6.153]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0248.002; Mon, 21 Sep 2015 09:52:56 -0500 From: "Serguei Bezverkhi (sbezverk)" To: "Ananyev, Konstantin" , "Van Haaren, Harry" , "dev@dpdk.org" Thread-Topic: getting pointer for struct ixgbe_hw Thread-Index: AdD0dZo794ndB0TST96I2nQYx9ybgAAAJkCgAAAuJRAAAOXp4AAAZnSA Date: Mon, 21 Sep 2015 14:52:56 +0000 Message-ID: References: <2601191342CEEE43887BDE71AB97725836A99BD1@irsmsx105.ger.corp.intel.com> In-Reply-To: <2601191342CEEE43887BDE71AB97725836A99BD1@irsmsx105.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.117.219.132] 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:53:33 -0000 Hi Konstantin, I need to setup certain parameters per VF from guest VM.=20 Here is the list: #define IXGBE_VF_RESET 0x01 /* VF requests reset= */ #define IXGBE_VF_SET_MAC_ADDR 0x02 /* VF requests PF to set MAC addr *= / #define IXGBE_VF_SET_MULTICAST 0x03 /* VF requests PF to set MC addr = */ #define IXGBE_VF_SET_VLAN 0x04 /* VF requests PF to set VLAN */ #define IXGBE_VF_SET_LPE 0x05 /* VF requests PF to set VMOLR.LPE */ #define IXGBE_VF_SET_MACVLAN 0x06 /* VF requests PF for unicast fil= ter */ #define IXGBE_VF_API_NEGOTIATE 0x08 /* negotiate API version */ #define IXGBE_VF_API_NEGOTIATE 0x08 /* negotiate API = version */ #define IXGBE_VF_GET_QUEUES 0x09 /* get queue co= nfiguration */ #define IXGBE_VF_ENABLE_MACADDR 0x0A /* enab= le MAC address */ #define IXGBE_VF_DISABLE_MACADDR 0x0B /* disable MAC address = */ #define IXGBE_VF_GET_MACADDRS 0x0C /* get all configure= d MAC addrs */ #define IXGBE_VF_SET_MCAST_PROMISC 0x0D /* enable multicast promis= cuous */ #define IXGBE_VF_GET_MTU 0x0E /* get bounds on MTU */ #define IXGBE_VF_SET_MTU 0x0F /* set a specific MTU */=20 The only way I found so far was directly using mailbox facility between PF = and VF. If you can suggest more proper way of doing it, I would appreciate = if you let me know. Thank you Serguei Serguei Bezverkhi, TECHNICAL LEADER.SERVICES Global SP Services sbezverk@cisco.com Phone:=A0+1 416 306 7312 Mobile:=A0+1 514 234 7374 CCIE (R&S,SP,Sec) - #9527 Cisco.com =A0Think before you print. This email may contain confidential and privileged material for the sole us= e of the intended recipient. Any review, use, distribution or disclosure by= others is strictly prohibited. If you are not the intended recipient (or a= uthorized 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. -----Original Message----- From: Ananyev, Konstantin [mailto:konstantin.ananyev@intel.com]=20 Sent: Monday, September 21, 2015 10:41 AM To: Serguei Bezverkhi (sbezverk) ; Van Haaren, Harry ; dev@dpdk.org Subject: RE: getting pointer for struct ixgbe_hw Hi Serguei, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Serguei Bezverkhi=20 > (sbezverk) > 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 =20 > ixgbe_hw because I needed access to ixgbe PF/VF mailbox facility. I am no= t 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=20 > sole use of the intended recipient. Any review, use, distribution or=20 > 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=20 > > access to ixgbe_hw structure for already initialized ixgbe nic. I=20 > > 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=20 > 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