From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: RE: [PATCH] eal: choose IOVA mode according to compilation flags
Date: Thu, 13 Apr 2023 09:42:58 +0000 [thread overview]
Message-ID: <DM6PR12MB375397C6C8ED3EEEB5903048DF989@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D87869@smartserver.smartshare.dk>
> -----Original Message-----
> From: Morten Brørup <mb@smartsharesystems.com>
> Sent: среда, 12 апреля 2023 г. 22:12
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>;
> david.marchand@redhat.com
> Subject: RE: [PATCH] eal: choose IOVA mode according to compilation flags
>
> > From: Viacheslav Ovsiienko [mailto:viacheslavo@nvidia.com]
> > Sent: Wednesday, 12 April 2023 19.20
> >
> > The DPDK can be compiled to be run in IOVA VA mode with
> > 'enable_iova_as_pa=false' meson option. If there is no explicit EAL
> > --iova-mode parameter specified in the command line the rte_eal_init()
> > tried to deduce VA or PA mode without taking into account the above
> > mentioned compile time option, resulting into initialization failure.
> >
> > Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> > ---
> > lib/eal/linux/eal.c | 5 ++++-
>
> This patch is close to being a bugfix. Good catch!
>
> You could also consider another patch, logging warnings in
> rte_bus_get_iommu_class() [1] for the busses that want IOVA as PA when
> !RTE_IOVA_IN_MBUF.
Yes, looks reasonable, thank you.
Let me gather the comments first, then will update the patch.
>
> [1]:
> https://elixir.bootlin.com/dpdk/v23.03/source/lib/eal/common/eal_common_
> bus.c#L224
>
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/lib/eal/linux/eal.c b/lib/eal/linux/eal.c index
> > c37868b7f0..4481bc4ad8 100644
> > --- a/lib/eal/linux/eal.c
> > +++ b/lib/eal/linux/eal.c
> > @@ -1080,7 +1080,10 @@ rte_eal_init(int argc, char **argv)
> > if (iova_mode == RTE_IOVA_DC) {
> > RTE_LOG(DEBUG, EAL, "Buses did not request a
> specific IOVA
> > mode.\n");
> >
> > - if (!phys_addrs) {
> > + if (!RTE_IOVA_IN_MBUF) {
> > + iova_mode = RTE_IOVA_VA;
> > + RTE_LOG(DEBUG, EAL, "IOVA VA mode is
> forced by
> > build option.\n");
>
> Minor detail regarding conventions: "IOVA VA " -> "IOVA as VA"
>
> > + } else if (!phys_addrs) {
> > /* if we have no access to physical addresses,
> > * pick IOVA as VA mode.
> > */
> > --
> > 2.18.1
>
> Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2023-04-13 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 17:19 Viacheslav Ovsiienko
2023-04-12 19:12 ` Morten Brørup
2023-04-13 9:42 ` Slava Ovsiienko [this message]
2023-06-06 15:15 ` [PATCH v2] " Viacheslav Ovsiienko
2023-06-06 15:23 ` Bruce Richardson
2023-06-07 16:48 ` Thomas Monjalon
2023-06-08 15:45 ` [PATCH v3] " Viacheslav Ovsiienko
2023-06-12 17:41 ` 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=DM6PR12MB375397C6C8ED3EEEB5903048DF989@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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).