From: EJ Raymond <eraymond00@gmail.com>
To: beilei.xing@intel.com
Cc: ferruh.yigit@intel.com, dev@dpdk.org, qi.z.zhang@intel.com,
helin.zhang@intel.com
Subject: Re: [dpdk-dev] Bypass support in the i40e PMD driver
Date: Wed, 5 Dec 2018 16:02:13 -0500 [thread overview]
Message-ID: <CAM8_=zBLAdypaOcev=Apv7xwE6buZpYHgokX4ZjR-Sj9oOjESQ@mail.gmail.com> (raw)
In-Reply-To: <94479800C636CB44BD422CB454846E01321F305B@SHSMSX101.ccr.corp.intel.com>
Hi,
Just wondering if there's any change in status of this topic? I can
currently access bypass support for this card in the Silicom utility
driver, but have no access in the current DPDK-18.11.0. Will there be
support similar to the 82599 bypass API in the future?
Thanks,
EJ
On Tue, Jul 24, 2018 at 2:15 AM Xing, Beilei <beilei.xing@intel.com> wrote:
>
>
> > -----Original Message-----
> > From: Yigit, Ferruh
> > Sent: Tuesday, July 24, 2018 4:42 AM
> > To: EJ Raymond <eraymond00@gmail.com>; dev@dpdk.org
> > Cc: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <
> qi.z.zhang@intel.com>;
> > Zhang, Helin <helin.zhang@intel.com>
> > Subject: Re: [dpdk-dev] Bypass support in the i40e PMD driver
> >
> > On 7/20/2018 7:39 PM, EJ Raymond wrote:
> > > Hi,
> > >
> > > I'm currently working with the PE310G4BPI71 Bypass card from Silicom,
> > > Inc., This board is based on the i40E chip (Intel X710 - Fortville).
> > > In DPDK, this card makes use of the i40e PMD driver, and I've noticed
> > > that bypass configuration is only supported in the IXGBE PMD driver
> > > today. Can anyone say if there'll be support for configuring the
> > > various bypass modes and watchdog timer in the librte_pmd_i40e driver
> in
> > the future?
> >
> > cc'ed i40e maintainers.
> >
>
> Sorry I didn't hear anything about i40e bypass related currently.
>
> > >
> > > Thanks,
> > > EJ
> > >
>
>
prev parent reply other threads:[~2018-12-05 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 18:39 EJ Raymond
2018-07-23 20:42 ` Ferruh Yigit
2018-07-24 6:14 ` Xing, Beilei
2018-12-05 21:02 ` EJ Raymond [this message]
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='CAM8_=zBLAdypaOcev=Apv7xwE6buZpYHgokX4ZjR-Sj9oOjESQ@mail.gmail.com' \
--to=eraymond00@gmail.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.com \
--cc=qi.z.zhang@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).