From: Stephen Hemminger <stephen@networkplumber.org>
To: F32 <feng32@163.com>
Cc: users@dpdk.org
Subject: Re: l2fwd: Requested device 0000:02:00.0 cannot be used (Ubuntu 22.04, DPDK 22.07, N5095, I225-V)
Date: Tue, 20 Sep 2022 08:16:25 -0700 [thread overview]
Message-ID: <20220920081625.2a307107@hermes.local> (raw)
In-Reply-To: <1f974932.6f93.1835a928c39.Coremail.feng32@163.com>
On Tue, 20 Sep 2022 19:04:57 +0800 (CST)
F32 <feng32@163.com> wrote:
> Hi Stephen,
>
>
> I have checked related iommu_groups:
>
>
> $ readlink 0000\:01\:00.0/iommu_group
>
> ../../../../kernel/iommu_groups/16
>
> $ readlink 0000\:02\:00.0/iommu_group
>
> ../../../../kernel/iommu_groups/17
>
> $ readlink 0000\:03\:00.0/iommu_group
>
> ../../../../kernel/iommu_groups/18
>
> $ readlink 0000\:04\:00.0/iommu_group
>
> ../../../../kernel/iommu_groups/19
>
> $ readlink 0000\:05\:00.0/iommu_group
>
> ../../../../kernel/iommu_groups/20
>
>
>
> It seems that the adapters belongs to different iommu_groups.
The way I would fix it is add instrumentation (ie printf) in EAL
code where the can not be used message is and work backwards from there.
next prev parent reply other threads:[~2022-09-20 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 3:18 F32
2022-09-16 15:10 ` Stephen Hemminger
2022-09-20 11:04 ` F32
2022-09-20 15:16 ` Stephen Hemminger [this message]
2022-09-21 11:51 ` F32
2022-10-04 6:49 ` David Marchand
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=20220920081625.2a307107@hermes.local \
--to=stephen@networkplumber.org \
--cc=feng32@163.com \
--cc=users@dpdk.org \
/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).