From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: fxzhang@chpc.ict.ac.cn, "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Why don't we make mmap MAP_SHARED with /dev/zero possible?
Date: Wed, 3 Nov 1999 14:32:54 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.991103142946.27233D-100000@kanga.kvack.org> (raw)
In-Reply-To: <Pine.LNX.4.10.9911032119450.8864-100000@chiara.csoma.elte.hu>
On Wed, 3 Nov 1999, Ingo Molnar wrote:
> it's now an unconditional __GFP_HIGHMEM in my tree. HIGHMEM gfp()
> allocation automatically falls back to allocate in lowmem, if highmem
> lists are empty.
I'd like to look through the patches to see how you're doing things before
making any comments. Specifically, I want to look at the buffer head
address thing that was mentioned -- given that the devices that support
addressing memory above 4G will expect a 64 bit address, I don't think the
shift is the right way to go.
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-11-03 19:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <qwwzox6l3nh.fsf@sap.com>
1999-11-03 14:29 ` Ingo Molnar
1999-11-03 14:50 ` Eric W. Biederman
1999-11-03 16:46 ` Ingo Molnar
1999-11-03 18:55 ` Eric W. Biederman
1999-11-03 19:16 ` Eric W. Biederman
1999-11-03 20:24 ` Ingo Molnar
1999-11-03 19:32 ` Benjamin C.R. LaHaise [this message]
1999-11-03 21:41 ` Ingo Molnar
1999-10-26 1:57 fxzhang
1999-10-26 7:35 ` Christoph Rohland
1999-10-26 12:05 ` Stephen C. Tweedie
1999-10-26 12:07 ` Stephen C. Tweedie
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=Pine.LNX.3.96.991103142946.27233D-100000@kanga.kvack.org \
--to=blah@kvack.org \
--cc=fxzhang@chpc.ict.ac.cn \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
/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