From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
"dariusz.stojaczyk@intel.com" <dariusz.stojaczyk@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal: pick IOVA as PA if IOMMU is not available
Date: Fri, 26 Jul 2019 15:03:14 +0000 [thread overview]
Message-ID: <BYAPR18MB2424F2340765E28B261FAC19C8C00@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
> -----Original Message-----
> From: Anatoly Burakov <anatoly.burakov@intel.com>
> Sent: Thursday, July 25, 2019 4:36 PM
> To: dev@dpdk.org
> Cc: John McNamara <john.mcnamara@intel.com>; Marko Kovacevic
> <marko.kovacevic@intel.com>; dariusz.stojaczyk@intel.com;
> thomas@monjalon.net; david.marchand@redhat.com; Jerin Jacob
> Kollanukkaran <jerinj@marvell.com>
> Subject: [EXT] [PATCH v3] eal: pick IOVA as PA if IOMMU is not available
>
> ----------------------------------------------------------------------
> 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.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
>
> MCS lock provides scalability by spinning on a CPU/thread local variable @@
> -436,6 +442,16 @@ Known Issues
> =========================================================
>
>
> + * **Unsuitable IOVA mode may be picked as the default**
This section is not rendering in HTML page. Remove the first tab to fix it.
With above fix:
Tested-by: Jerin Jacob <jerinj@marvell.com>
Reviewed-by: Jerin Jacob <jerinj@marvell.com>
next reply other threads:[~2019-07-26 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 15:03 Jerin Jacob Kollanukkaran [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-25 9:52 [dpdk-dev] [PATCH v2] " Anatoly Burakov
2019-07-25 11:05 ` [dpdk-dev] [PATCH v3] " Anatoly Burakov
2019-07-26 5:08 ` Stojaczyk, Dariusz
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=BYAPR18MB2424F2340765E28B261FAC19C8C00@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=anatoly.burakov@intel.com \
--cc=dariusz.stojaczyk@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=thomas@monjalon.net \
/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).