From: "Thomas Monjalon" <thomas@monjalon.net>
To: "David Marchand" <david.marchand@redhat.com>,
"Anatoly Burakov" <anatoly.burakov@intel.com>
Cc: dev <dev@dpdk.org>, "Jerin Jacob Kollanukkaran" <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] eal: pick IOVA as PA if IOMMU is not available
Date: Thu, 25 Jul 2019 20:58:47 +0200 [thread overview]
Message-ID: <e1a49abb-110c-4151-8e81-eee2119d4970@www.fastmail.com> (raw)
In-Reply-To: <CAJFAV8xAvrY3AJX1eueYyxAZAkC4aE4p7UOfC9QrOLOx6HK8HA@mail.gmail.com>
Jeu 25 juil 2019, à 10:05, David Marchand a écrit :
> On Wed, Jul 24, 2019 at 6:46 PM Anatoly Burakov
> <anatoly.burakov@intel.com> wrote:
> >
> > When IOMMU is not available, /sys/kernel/iommu_groups will not be
> > populated. This is happening since at least 3.6 when VFIO support
> > was added. If the directory is empty, EAL should not pick IOVA as
> > VA as the default IOVA mode.
> >
> > We also assume that VFIO equals IOMMU, so if VFIO support is not
> > compiled, we always assume IOMMU support is not available.
>
> Not sure I agree with this statement.
> What about unknown (from eal pov) kernel drivers?
Exactly, this is the case of Mellanox drivers.
next prev parent reply other threads:[~2019-07-25 18:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 16:46 Anatoly Burakov
2019-07-25 8:05 ` David Marchand
2019-07-25 9:31 ` Burakov, Anatoly
2019-07-25 9:35 ` David Marchand
2019-07-25 9:38 ` Burakov, Anatoly
2019-07-25 9:40 ` Burakov, Anatoly
2019-07-25 18:58 ` Thomas Monjalon [this message]
2019-07-25 9:52 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov
2019-07-25 9:56 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-07-25 11:05 ` [dpdk-dev] [PATCH v3] " Anatoly Burakov
2019-07-26 5:08 ` Stojaczyk, Dariusz
2019-07-26 15:37 ` [dpdk-dev] [PATCH v4] " Anatoly Burakov
2019-07-29 9:31 ` David Marchand
2019-07-29 11:18 ` Burakov, Anatoly
2019-07-29 13:52 ` [dpdk-dev] [PATCH v5] " Anatoly Burakov
2019-07-30 7:21 ` David Marchand
2019-07-30 8:10 ` Thomas Monjalon
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=e1a49abb-110c-4151-8e81-eee2119d4970@www.fastmail.com \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.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).