From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: David Marchand <david.marchand@redhat.com>,
Ben Walker <benjamin.walker@intel.com>
Cc: dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"eric.zhang@windriver.com" <eric.zhang@windriver.com>
Subject: Re: [dpdk-dev] eal/pci: Improve automatic selection of IOVA mode
Date: Tue, 4 Jun 2019 11:28:29 +0000 [thread overview]
Message-ID: <BYAPR18MB242430ECC3D54A06B66FFB9CC8150@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
From: David Marchand <david.marchand@redhat.com>
Sent: Monday, June 3, 2019 4:19 PM
To: Ben Walker <benjamin.walker@intel.com>; Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev <dev@dpdk.org>; Burakov, Anatoly <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] eal/pci: Improve automatic selection of IOVA mode
> - This leaves the --iova-va forcing option.
> Why do we need it?
> If we don't have access to physical addresses, no choice but run in VA mode.
> If we have access to physical addresses, the only case would be that you want to downgrade from PA to VA.
> But well, your process can still access it, not sure what the benefit is.
> Jerin, I can see in the history you worked on this.
> What did I miss?
> Is there something wrong with dropping the detection code?
Its added by Eric to support virtual devices.
https://mails.dpdk.org/archives/dev/2018-September/111141.html
next reply other threads:[~2019-06-04 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 11:28 Jerin Jacob Kollanukkaran [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-30 17:48 Ben Walker
2019-06-03 10:48 ` David Marchand
2019-06-03 16:44 ` Walker, Benjamin
2019-06-14 8:42 ` 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=BYAPR18MB242430ECC3D54A06B66FFB9CC8150@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=anatoly.burakov@intel.com \
--cc=benjamin.walker@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=eric.zhang@windriver.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).