linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@chiara.csoma.elte.hu>
To: "Eric W. Biederman" <ebiederm+eric@ccr.net>
Cc: Christoph Rohland <hans-christoph.rohland@sap.com>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	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 21:24:17 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.10.9911032119450.8864-100000@chiara.csoma.elte.hu> (raw)
In-Reply-To: <m1bt9bv10u.fsf@flinx.hidden>

On 3 Nov 1999, Eric W. Biederman wrote:

> Q: Highmem allocation for the page cache.
> 
> Note:  page_cache_alloc currently doesn't take any parameters.
> It should take __GFP_BIGMEM or whatever so we can yes high memory is ok.

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.

> Or no.  
> I'm going to put metadata in this page and high memory is not o.k, too
> inconvienint.

hm, i see, this makes sense. permanent mappings are not inconvenient at
all (you can hold a number of them, can sleep inbetween), but maybe we
still want to allocate in low memory in some cases, for performance
reasons. It's not a problem at all and completely legal, as low memory
pages can happen anyway, so everything is completely symmetric. Any 'high
memory enabled code' automatically works with low memory (or exclusive low
memory) as well.

-- mingo

--
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/

  reply	other threads:[~1999-11-03 20:24 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 [this message]
1999-11-03 19:32           ` Benjamin C.R. LaHaise
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.4.10.9911032119450.8864-100000@chiara.csoma.elte.hu \
    --to=mingo@chiara.csoma.elte.hu \
    --cc=ebiederm+eric@ccr.net \
    --cc=fxzhang@chpc.ict.ac.cn \
    --cc=hans-christoph.rohland@sap.com \
    --cc=linux-mm@kvack.org \
    --cc=sct@redhat.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