DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jean-Philippe Longeray <Jean-Philippe.Longeray@viavisolutions.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Qi Zhang <qi.z.zhang@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: X710 VF not working anymore on DPDK 21.11
Date: Wed, 12 Jan 2022 09:41:21 +0000	[thread overview]
Message-ID: <SJ0PR18MB38503A1F35F3B608D905DDBCA9529@SJ0PR18MB3850.namprd18.prod.outlook.com> (raw)
In-Reply-To: <a09668be-a9fc-4d4d-1dc3-82e594afadb3@intel.com>



Thanks a lot!
Adding library librte_net_iavf.so solves the problem!
Nice!

JPL.
-----Message d'origine-----
De : Ferruh Yigit <ferruh.yigit@intel.com> 
Envoyé : mercredi 12 janvier 2022 10:28
À : Jean-Philippe Longeray <jpl69fr@hotmail.fr>
Cc : Qi Zhang <qi.z.zhang@intel.com>; Beilei Xing <beilei.xing@intel.com>; dev@dpdk.org
Objet : Re: X710 VF not working anymore on DPDK 21.11

EXTERNAL EMAIL: Do not click links or open attachments unless you know and trust the sender.


On 1/12/2022 9:07 AM, Jean-Philippe Longeray wrote:
> Hi All
>
> I use igb_uio or uio_pci_generic to bind X710 VF:
>
> 0000:00:07.0 'XL710/X710 Virtual Function 154c' drv=igb_uio unused=iavf,uio_pci_generic
>
> The problem is that the device is not probed anymore by DPDK!
>
> It works perfectly with 20.11.
>
> Any advice?


Hi Jean-Philippe,

i40evf driver is removed in 21.11, in favor of iavf [1], if this is what you mean.

But DPDK 'iavf' driver should probe it and same functionality should be available.


cc'ed i40e maintainers as well.


[1]:
fe2a571c70cc ("net/i40e: remove i40evf")

>
> Thank-you
>
> Jean-Philippe *Longeray*
>
> Senior Solution Architect
>
> *Expandium / Viavi Solutions*
>
> +33 6 76 48 34 95
>


      reply	other threads:[~2022-01-12  9:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  9:07 Jean-Philippe Longeray
2022-01-12  9:28 ` Ferruh Yigit
2022-01-12  9:41   ` Jean-Philippe Longeray [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=SJ0PR18MB38503A1F35F3B608D905DDBCA9529@SJ0PR18MB3850.namprd18.prod.outlook.com \
    --to=jean-philippe.longeray@viavisolutions.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).