From: Jacob Gorm Hansen <jacobg@diku.dk>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Linux question, user space virtual mem layout
Date: Fri, 08 Apr 2005 19:26:10 -0700 [thread overview]
Message-ID: <42573D42.4040705@diku.dk> (raw)
hi,
I am trying to allow dom0 to be mapped permanently in the top parts of
all domU address spaces, to save some TLB flushes when doing I/O (on
x86-32) and see how much that helps performance.
So far I have managed to get the dom0 kernel, and a relinked user space,
to live between 0xf0000000 and 0xfc000000 where Xen starts. But I have
the problem that even though me user-space binaries are linked to reside
in the 0xf0000000 -> 0xf6000000 virtual area, mmap() in Linux still
likes to create mappings below 0xf0000000.
Can anyone on this list tell me how I can instruct Linux not to go below
a certain address when dealing out virtual mappings to user-space?
Thanks in advance,
Jacob
next reply other threads:[~2005-04-09 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 2:26 Jacob Gorm Hansen [this message]
2005-04-09 2:58 ` Linux question, user space virtual mem layout Jacob Gorm Hansen
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=42573D42.4040705@diku.dk \
--to=jacobg@diku.dk \
--cc=xen-devel@lists.xensource.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 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.