From: "Martin Drašar" <drasar@ics.muni.cz>
To: dev@dpdk.org
Subject: [dpdk-dev] Using bypass on Silicom PE210G2BPi9 with Intel 82599ES chip
Date: Wed, 18 Feb 2015 11:20:54 +0100 [thread overview]
Message-ID: <54E46786.1050602@ics.muni.cz> (raw)
Hi,
I hope that I am using the correct mailing list...
I have a Silicom PE210G2BPi9 LR card with Intel 82599ES chip that has a
bypass. Now I would like to turn the bypass on and off from software.
However, I am having some problems with it.
I am able to check whether the card supports the bypass (i.e. for a card
without bypass it shows me that bypass is not supported and for this one
is), but I am not able to correctly get or set the bypass mode.
If I call the following:
uint32_t bypassState;
rc = rte_eth_dev_bypass_state_show(port, &bypassState);
Then the bypass state is always 0, which, according to documentation, is
not a valid value. The same goes for rte_eth_dev_bypass_state_set.
Does the DPDK support this card and this functionality?
I am currently using DPDK 1.5.2r1.
Thank you.
Martin
reply other threads:[~2015-02-18 10:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54E46786.1050602@ics.muni.cz \
--to=drasar@ics.muni.cz \
--cc=dev@dpdk.org \
/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).