From: Bruce Richardson <bruce.richardson@intel.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: dev <dev@dpdk.org>, conor.walsh@intel.com, kevin.laatz@intel.com
Subject: Re: Using IOAT PMD
Date: Thu, 16 Dec 2021 16:20:29 +0000 [thread overview]
Message-ID: <YbtnTQROE2P8flZ1@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CADyeNECkRa3gSW_yoKMLi=0LUBz=uFH33oH-QTFai1m=uqC=Wg@mail.gmail.com>
On Thu, Dec 16, 2021 at 11:04:54AM -0500, Lance Richardson wrote:
> Hi Bruce,
>
> I've been looking into using the IOAT PMD, initially with dma_autotest
> and the dpdk-dma example application. These seem to work fine on
> SKX with the current main branch, but when I try the same procedure
> on ICX (binding all 8 devices to vfio-pci in both cases), I get the following
> output for each device when probed. Is something different needed when
> using IOAT on ICX vs. SKX?
>
> Thanks,
> Lance
>
> EAL: Probe PCI driver: dmadev_ioat (8086:b00) device: 0000:80:01.0 (socket 2)
> IOAT: ioat_dmadev_probe(): Init 0000:80:01.0 on NUMA node 2
> IOAT: ioat_dmadev_create(): ioat_dmadev_create: Channel count == 255
>
> IOAT: ioat_dmadev_create(): ioat_dmadev_create: Channel appears locked
>
> IOAT: ioat_dmadev_create(): ioat_dmadev_create: cannot reset device.
> CHANCMD=0xff, CHANSTS=0xffffffffffffffff, CHANERR=0xffffffff
>
> EAL: Releasing PCI mapped resource for 0000:80:01.0
> EAL: Calling pci_unmap_resource for 0000:80:01.0 at 0x4102430000
> EAL: Requested device 0000:80:01.0 cannot be used
That is strange, the same PMD should work ok on both platforms. This is all
on latest branch, right? Let me attempt to reproduce and get back to you.
/Bruce
PS: Is this a 4-socket system you are running on, since I see "socket 2"
being described as the socket number for device 80:01.0?
next prev parent reply other threads:[~2021-12-16 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 16:04 Lance Richardson
2021-12-16 16:20 ` Bruce Richardson [this message]
2021-12-16 16:34 ` Lance Richardson
2021-12-16 17:33 ` Bruce Richardson
2021-12-16 19:08 ` Lance Richardson
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=YbtnTQROE2P8flZ1@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--cc=lance.richardson@broadcom.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).