From: Avner Taieb <avner@reduxio.com>
To: "Roberts, Lee A." <lee.roberts@hpe.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Need Help for Intel - i40e , XL710 40GbE Controller
Date: Wed, 4 Mar 2020 20:05:27 +0200 [thread overview]
Message-ID: <CANBJLZEzZeYPqDG1L=fd6_xMkfKBHW_YXSGFZJSRVABF=ev0AQ@mail.gmail.com> (raw)
In-Reply-To: <DF4PR8401MB12428AF326E56E49598CF252E5E50@DF4PR8401MB1242.NAMPRD84.PROD.OUTLOOK.COM>
Thanks Lee. I already read it and tried the potential remedy that is
suggested i.e. enabling the multi driver support , but it didn't solved the
problem.
Are there more setting documented anywhere ?
On Wed, Mar 4, 2020 at 7:33 PM Roberts, Lee A. <lee.roberts@hpe.com> wrote:
> See https://www.kernel.org/doc/Documentation/networking/i40e.rst, in
> particular,
> read the paragraph on "Unexpected Issues when the device driver and DPDK
> share a device".
>
> - Lee
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Avner Taieb
> Sent: Wednesday, March 4, 2020 9:48 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Need Help for Intel - i40e , XL710 40GbE Controller
>
> Hi,
> I am using XL710 40GbE Controller with two ports.
> The way I am using them is one port is configured to vfio-pci for using
> with dpdk in user space and the other is left to the kernel driver and for
> a seperate application that does not use DPDK.
> As soon as DPDK initialize and start the port, the other port
> become unusable.
>
> Is there any setting/configuration that I am missing ?
>
> Thanks,
> Avner
>
next prev parent reply other threads:[~2020-03-04 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 16:48 Avner Taieb
2020-03-04 17:33 ` Roberts, Lee A.
2020-03-04 18:05 ` Avner Taieb [this message]
2020-03-05 9:23 ` Bruce Richardson
2020-03-05 14:11 ` Avner Taieb
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='CANBJLZEzZeYPqDG1L=fd6_xMkfKBHW_YXSGFZJSRVABF=ev0AQ@mail.gmail.com' \
--to=avner@reduxio.com \
--cc=dev@dpdk.org \
--cc=lee.roberts@hpe.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).