From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Don Wallwork <donw@xsightlabs.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [RFC] EAL: legacy memory fixed address translations
Date: Thu, 28 Jul 2022 10:25:37 +0300 [thread overview]
Message-ID: <20220728102537.48ff6e5f@sovereign> (raw)
In-Reply-To: <e2501444-cbb7-9a41-a9f1-fda211d385fb@xsightlabs.com>
2022-07-27 17:43 (UTC-0400), Don Wallwork:
> On 7/27/2022 4:36 PM, Dmitry Kozlyuk wrote:
> > I now understand more about_why_ you want this feature
> > but became less confident_what_ do you're proposing specifically.
>
> Let me try to give a trivial example of how it would work
> to make sure we're on the same page and then we can get
> back to details..
Thanks you, Don.
Now it's perfectly clear what EAL should do and we can discuss API.
[...]
> So in this example, we have a fixed offset of 9G to translate
> between VA to PA or vice versa.This works whether the huge
> pages happen to be allocated statically (legacy mode) or
> dynamically.
True!
One special case is external memory (rte_extmem_*)
which has user-controlled VA and IOVA.
If all non-external memory is mapped within one VA region,
it is possible to detect that an address is in external memory,
although it's an extra check.
next prev parent reply other threads:[~2022-07-28 7:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 18:18 RFC: EAL " Don Wallwork
2022-07-26 18:33 ` [RFC] EAL: " Don Wallwork
2022-07-26 19:59 ` Dmitry Kozlyuk
2022-07-27 17:20 ` Don Wallwork
2022-07-27 19:12 ` Stephen Hemminger
2022-07-27 19:27 ` Don Wallwork
2022-07-27 20:36 ` Dmitry Kozlyuk
2022-07-27 21:43 ` Don Wallwork
2022-07-28 7:25 ` Dmitry Kozlyuk [this message]
2022-07-28 11:29 ` Morten Brørup
2022-07-28 14:46 ` Don Wallwork
2022-07-28 15:41 ` Don Wallwork
2022-07-28 16:33 ` Dmitry Kozlyuk
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=20220728102537.48ff6e5f@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=donw@xsightlabs.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).