From: Andrea Arcangeli <andrea@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-mm@kvack.org, alan@lxorguk.ukuu.org.uk,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: RFC: Bouncebuffer fixes
Date: Sun, 29 Apr 2001 15:17:11 +0200 [thread overview]
Message-ID: <20010429151711.A11395@athlon.random> (raw)
In-Reply-To: <20010429035626.B14210@devserv.devel.redhat.com>; from arjanv@redhat.com on Sun, Apr 29, 2001 at 03:56:26AM -0400
On Sun, Apr 29, 2001 at 03:56:26AM -0400, Arjan van de Ven wrote:
> This looks like the code in Alan's tree around 2.4.3-ac7, and that is NOT
> enough to fix the deadlock. With that patch, tests deadlock within 10 minutes....
>
> One of the reasons it deadlocks is because GFP_BUFFER can sleep here,
> without the guarantee of progress. The regular VM threads that should
GFP_BUFFER doesn't provide guarantee of progress and that's fine, as far
as GFP_BUFFER allocations returns NULL eventually there should be no
problem. The fact some emergency buffer is in flight is just the guarantee
of progress because after unplugging tq_disk we know those emergency
buffers will be released without the need of further memory allocations.
If GFP_BUFFER allocation never returns and they deadlocks inside the VM
that's a completly unrelated bug and I think you shouldn't workaround it
in highmem.c.
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:[~2001-04-29 13:17 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 [this message]
2001-04-29 13:41 ` Arjan van de Ven
2001-04-29 14:10 ` Andrea Arcangeli
2001-04-30 13:53 ` anti-deadlock logic (was Re: RFC: Bouncebuffer fixes) Szabolcs Szakacsits
2001-04-29 13:42 ` RFC: Bouncebuffer fixes 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=20010429151711.A11395@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.