From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@nl.linux.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.rutgers.edu>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] 2.2.1{3,4,5} VM fix
Date: Fri, 21 Jan 2000 13:54:26 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.21.0001211353200.486-100000@alpha.random> (raw)
In-Reply-To: <Pine.LNX.4.10.10001210337350.27593-100000@mirkwood.dummy.home>
On Fri, 21 Jan 2000, Rik van Riel wrote:
>Below .min only GFP_ATOMIC and PF_MEMALLOC allocations
>should be allowed.
>
>This is how the priorities have been intended
>from the start on (except that we didn't have the
Very wrong. Since 2.1.x all GFP_KERNEL allocations (not atomic) succeed
too.
Andrea
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-01-21 12:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-19 21:15 Rik van Riel
2000-01-20 17:11 ` Andrea Arcangeli
2000-01-20 20:30 ` Rik van Riel
2000-01-21 0:42 ` Andrea Arcangeli
2000-01-21 0:56 ` Alan Cox
2000-01-21 2:08 ` Andrea Arcangeli
2000-01-21 2:43 ` Rik van Riel
2000-01-21 12:54 ` Andrea Arcangeli [this message]
2000-01-21 19:18 ` Rik van Riel
2000-01-22 2:43 ` Andrea Arcangeli
2000-01-22 3:22 ` Benjamin C.R. LaHaise
2000-01-22 14:02 ` Andrea Arcangeli
2000-01-24 13:21 ` GFP_XXX semantics (was: Re: [PATCH] 2.2.1{3,4,5} VM fix) Ingo Oeser
2000-01-24 15:08 ` Andrea Arcangeli
2000-01-25 0:01 ` Rik van Riel
[not found] ` <Pine.LNX.4.10.10001241411310.24852-100000@nightmaster.csn. tu-chemnitz.de>
2000-01-24 13:40 ` Andi Kleen
2000-01-21 1:12 ` [PATCH] 2.2.1{3,4,5} VM fix Rik van Riel
2000-01-21 2:01 ` Andrea Arcangeli
2000-01-21 2:36 ` Andrea Arcangeli
2000-01-21 2:37 ` Rik van Riel
2000-01-21 13:24 ` Andrea Arcangeli
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.21.0001211353200.486-100000@alpha.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.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