DPDK usage discussions
 help / color / mirror / Atom feed
From: "Johnson, Brian" <brian.johnson@intel.com>
To: Igor Genuino <igenuino@sandvine.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Set device id to 0x1889 to use DPDK IAVF
Date: Tue, 8 Mar 2022 16:38:27 +0000
Message-ID: <B130377A-1609-4A1C-AD07-76EE45D3546D@intel.com> (raw)
In-Reply-To: <f6bcd52f591746c882c925c39067ffb9@sandvine.com>

[-- Attachment #1: Type: text/plain, Size: 1742 bytes --]

Depending on which version of DPKD you are using a VF on the 700 Series will use either the i40evf or iavf PMD. In 21.11 the i40evf PMD has been removed and will use iavf for both 700 and 800 Series controllers. The 700 Series does not use the 1889 device ID since iavf was introduced after we released the 700 Series. The kernel mode iavf driver has supported both the 700 and 800 Series VF device ids for several years now but it took a while to transition DPDK over to a single iavf driver.

If the i40evf PMD is not available in a VM and the iavf PMD is then you can pass the 1889 device ID but this is would only be required on pre-21.11 DPDK version.

-device vfio-pci,x-pci-device-id=0x1889,host=03:0a.0.

Brian Johnson

On Mar 8, 2022, at 1:19 AM, Igor Genuino <igenuino@sandvine.com> wrote:

Hello all users.
I need some support.
The following text isn't clear for me:

"To use DPDK IAVF PMD on Intel® 700 Series Ethernet Controller, the device id (0x1889) need to specified during device assignment in hypervisor. " (https://doc.dpdk.org/guides/nics/intel_vf.html)

I am using an i40e in the hypervisor.

Is it necessary to set the device id to 0x1889 in order to use DPDK IAVF?

This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is considered confidential, proprietary, sensitive and/or otherwise legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation.

[-- Attachment #2: Type: text/html, Size: 3992 bytes --]

      reply	other threads:[~2022-03-08 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  7:45 Igor Genuino
2022-03-08 16:38 ` Johnson, Brian [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B130377A-1609-4A1C-AD07-76EE45D3546D@intel.com \
    --to=brian.johnson@intel.com \
    --cc=igenuino@sandvine.com \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git