From: "Yang, Qiming" <qiming.yang@intel.com>
To: "Chen, Sam" <samchen@aaeon.com.tw>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: DPDK with i225/226 on elkhartlake
Date: Fri, 23 Sep 2022 07:50:50 +0000 [thread overview]
Message-ID: <MWHPR11MB188610ECB258FC23FDE0734BE5519@MWHPR11MB1886.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SI2PR02MB582674ACA9D4EC406736C61F834E9@SI2PR02MB5826.apcprd02.prod.outlook.com>
Hi, Sam
We don't support I225-IT in 22.07 release, you can update you code to the latest next-net-intel branch, it contain the fix.
But for i226v's log, I don't see any issue, seems 06:00.0 init success. Could you clarify it?
Qiming
> -----Original Message-----
> From: SamChen 陳嘉良 <SamChen@aaeon.com.tw>
> Sent: Thursday, September 22, 2022 10:57 AM
> To: Richardson, Bruce <bruce.richardson@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: DPDK with i225/226 on elkhartlake
>
> Hi all,
> I have switched to using vfio-pci, but still can't use DPDK. Attached are the
> logs I can't use in I225-IT and I226V for your reference.
> If I have obtained other platforms with intel 225/226 systems, I will check
> again, thanks!
>
> Sam Chen
>
> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>
> Sent: Wednesday, September 21, 2022 4:57 PM
> To: SamChen 陳嘉良 <SamChen@aaeon.com.tw>
> Cc: dev@dpdk.org
> Subject: Re: DPDK with i225/226 on elkhartlake
>
> On Wed, Sep 21, 2022 at 03:23:09AM +0000, SamChen 陳嘉良 wrote:
> > Hi,
> > We bind the uio_pci_generic driver and use the command of the attached
> > image to execute DPDK. However, we encountered the problem of device
> > cannot be used on i225V/i226V in elkhartlake platform. Currently, the
> > same method works fine for i211 and intel® Killer™ Ethernet E3100 2.5
> > Gbps. Do you have any suggestions? Thanks!
> >
> Hi,
>
> while I can't comment on the NIC-specific issues, I would just comment that
> it's really not recommended to use uio_pci_generic - or any other uio driver -
> for DPDK any more. You should consider switching to using vfio-pci. Even if
> there is no iommu enabled, vfio-pci still tends to give a better user
> experience. If iommu is enabled, you also get a lot more security from the
> memory protection it provides.
>
> Regards,
> /Bruce
next prev parent reply other threads:[~2022-09-23 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 3:23 SamChen 陳嘉良
2022-09-21 8:56 ` Bruce Richardson
2022-09-22 2:56 ` SamChen 陳嘉良
2022-09-23 7:50 ` Yang, Qiming [this message]
2022-09-23 8:28 ` SamChen 陳嘉良
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=MWHPR11MB188610ECB258FC23FDE0734BE5519@MWHPR11MB1886.namprd11.prod.outlook.com \
--to=qiming.yang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=samchen@aaeon.com.tw \
/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).