From: Andi Kleen <ak@muc.de>
To: "David S. Miller" <davem@redhat.com>
Cc: andrea@suse.de, linux-kernel@vger.kernel.org
Subject: Re: mincore on anon mappings
Date: Sun, 20 Jun 2004 02:05:19 +0200 [thread overview]
Message-ID: <m33c4rrt4w.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <28Tev-1Bm-23@gated-at.bofh.it> (David S. Miller's message of "Sat, 19 Jun 2004 21:00:15 +0200")
"David S. Miller" <davem@redhat.com> writes:
>
> Therefore I propose we add a MAP_FORCE which does exactly what GCC wants
> which is:
>
> 1) The passed in 'hint' address is treated as mandatory, if exactly that
> address cannot be used, we fail.
>
> 2) Existing areas get in the way, and cause failure.
That sounds unintuitive. I would expect MAP_FORCE to do exactly
that (that is is done by default right now is a different story).
But you want to reverse the meaning.
How about calling it MAP_STRICT or just MAP_CHECK ?
>
> 3) get_unmapped_area() implementations shut off any 'hint' address
> modification logic they may have.
Good idea definitely.
-Andi
next parent reply other threads:[~2004-06-19 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <28R2T-8ld-13@gated-at.bofh.it>
[not found] ` <28Tev-1Bm-23@gated-at.bofh.it>
2004-06-20 0:05 ` Andi Kleen [this message]
2004-06-19 22:50 ` mincore on anon mappings David S. Miller
2004-06-19 16:25 Andrea Arcangeli
2004-06-19 18:54 ` David S. Miller
2004-06-19 21:55 ` William Lee Irwin III
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=m33c4rrt4w.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox