From: Szabolcs Szakacsits <szaka@f-secure.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Arjan van de Ven <arjanv@redhat.com>,
linux-mm@kvack.org, alan@lxorguk.ukuu.org.uk,
Linus Torvalds <torvalds@transmeta.com>,
"Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Subject: anti-deadlock logic (was Re: RFC: Bouncebuffer fixes)
Date: Mon, 30 Apr 2001 15:53:52 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.4.30.0104301525240.16238-100000@fs131-224.f-secure.com> (raw)
In-Reply-To: <20010429161012.F11395@athlon.random>
On Sun, 29 Apr 2001, Andrea Arcangeli wrote:
> Note that the fact GFP_BUFFER fails or succeed is absolutely not
> interesting and unrelated to the anti-deadlock logic.
May I ask what's the anti-deadlock logic? Because it does not work [see
all kind of MM related hangs, livelocks on lkml]. As for 2.4.4 only
GFP_ATOMIC, kswapd, reclaimd, mtdblockd and OOM killed process
allocations can return NULL [from __alloc_pages()], all others will loop
until the requested free page(s) become available.
Szaka
--
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:[~2001-04-30 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 21:06 RFC: Bouncebuffer fixes Arjan van de Ven
2001-04-29 0:07 ` Andrea Arcangeli
2001-04-29 7:56 ` Arjan van de Ven
2001-04-29 13:17 ` Andrea Arcangeli
2001-04-29 13:41 ` Arjan van de Ven
2001-04-29 14:10 ` Andrea Arcangeli
2001-04-30 13:53 ` Szabolcs Szakacsits [this message]
2001-04-29 13:42 ` Andrea Arcangeli
2001-05-01 8:14 ` Ingo Molnar
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.30.0104301525240.16238-100000@fs131-224.f-secure.com \
--to=szaka@f-secure.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=arjanv@redhat.com \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.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