All of lore.kernel.org
 help / color / mirror / Atom feed
From: ruben@mrbrklyn.com (Ruben Safir)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Translating physical/linear address to virtual address
Date: Sat, 03 Oct 2015 00:29:34 -0400	[thread overview]
Message-ID: <560F59AE.6040405@mrbrklyn.com> (raw)
In-Reply-To: <20151003040452.GA2106@gamayun>

On 10/03/2015 12:04 AM, Martin Ichilevici de Oliveira wrote:
> My goal is to use this data to make informed decisions on pages
> distribution in NUMA machines (with libnuma). The problem is that, as
> far as I understood, physical and linear addresses won't necessarily be
> the same between runs of the same program. Virtual addresses, on the
> other hand, can be made to be consistent (by turning address space layout
> randomization off).
> 
> Using virtual addresses also have the advantage that I can do all memory
> management in userspace, with libnuma.


Your not really understanding some basic architectural problems.  Memory
is shifted from segment to segment, the OS has paging, the hardware
hides memory addressing as well, and then there is DME.  How the
motherboard chips lays out and allows access to memory segments is not
something that can be manually controlled, even by the OS because it is
firmware driven.

I'm not saying that what you are doing is impossible, but it doesn't
sound like you approach is likely to work.


http://www.nylxs.com/docs/grad_school/arch/memory.pdf

http://www.nylxs.com/docs/grad_school/arch/

      reply	other threads:[~2015-10-03  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 19:58 Translating physical/linear address to virtual address martin
     [not found] ` <CAK7N6vpy3g022b+Au_uQqAEF4aK3g24702VcFnvxXCeJVe8SLw@mail.gmail.com>
2015-10-03  4:04   ` Martin Ichilevici de Oliveira
2015-10-03  4:29     ` Ruben Safir [this message]

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=560F59AE.6040405@mrbrklyn.com \
    --to=ruben@mrbrklyn.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.