From: Sharath <sharathjm.bharadwaj@gmail.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] are these bypass api supported on Intel Bandon Beach card : of device id : 8086:155d
Date: Tue, 4 Mar 2014 12:17:04 +0530 [thread overview]
Message-ID: <CAJ6BMtAv95FZ24fj=Rab+4TZ3iNWLwfaw1sEcp-fNVvD=BBJ=A@mail.gmail.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725808E7A34D@IRSMSX105.ger.corp.intel.com>
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
bypass and normal state. it is not working
assume in the first run I will put the NIC into bypass
then leave for 5 min
later, in second run if I make the NIC into norm state using the same set
of 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 <
konstantin.ananyev@intel.com> 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=y in your config
> 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
> Beach 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 <sharathjm.bharadwaj@gmail.com
> >wrote:
>
> > 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
> >
>
next prev parent reply other threads:[~2014-03-04 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 11:36 Sharath
2014-03-03 6:13 ` Sharath
2014-03-03 10:24 ` Ananyev, Konstantin
2014-03-04 6:47 ` Sharath [this message]
2014-03-04 15:33 ` 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='CAJ6BMtAv95FZ24fj=Rab+4TZ3iNWLwfaw1sEcp-fNVvD=BBJ=A@mail.gmail.com' \
--to=sharathjm.bharadwaj@gmail.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).