From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Serguei Bezverkhi (sbezverk)" <sbezverk@cisco.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] getting pointer for struct ixgbe_hw
Date: Mon, 21 Sep 2015 14:41:29 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725836A99BD1@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <EDCEC56DA1E05E428B0B5FBB4D07139216DA6397@xmb-rcd-x06.cisco.com>
Hi Serguei,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Serguei Bezverkhi (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
>
> Hi Harry,
>
> Thank you for your reply. The reason I was looking for specifically ixgbe_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.
Wonder what exactly you are trying to achieve?
Konstantin
>
> Best regards
>
> Serguei
>
>
> Serguei Bezverkhi,
> TECHNICAL LEADER.SERVICES
> Global SP Services
> sbezverk@cisco.com
> Phone: +1 416 306 7312
> Mobile: +1 514 234 7374
>
> CCIE (R&S,SP,Sec) - #9527
>
> Cisco.com
>
>
>
> Think 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 click here for Company Registration Information.
>
>
>
> -----Original Message-----
> From: Van Haaren, Harry [mailto:harry.van.haaren@intel.com]
> Sent: Monday, September 21, 2015 10:06 AM
> To: Serguei Bezverkhi (sbezverk) <sbezverk@cisco.com>; dev@dpdk.org
> Subject: RE: getting pointer for struct ixgbe_hw
>
> Hi Serguei,
>
> > 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 pointer for this structure.
>
> 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.
>
> Hope that helps, -Harry
>
> [1] http://www.dpdk.org/doc/api/rte__ethdev_8h.html
next prev parent reply other threads:[~2015-09-21 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 13:58 Serguei Bezverkhi (sbezverk)
2015-09-21 14:06 ` Van Haaren, Harry
2015-09-21 14:11 ` Serguei Bezverkhi (sbezverk)
2015-09-21 14:41 ` Ananyev, Konstantin [this message]
2015-09-21 14:52 ` Serguei Bezverkhi (sbezverk)
2015-09-21 15:27 ` Ananyev, Konstantin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2601191342CEEE43887BDE71AB97725836A99BD1@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=sbezverk@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).