From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [RFC][PATCH] mm: balance_dirty_pages() vs throttle_vm_writeout() deadlock
Date: Mon, 26 Feb 2007 15:10:51 +0100 [thread overview]
Message-ID: <1172499051.6374.56.camel@twins> (raw)
In-Reply-To: <1172497438.6374.53.camel@twins>
On Mon, 2007-02-26 at 14:43 +0100, Peter Zijlstra wrote:
> It might, but I'm afraid that the NFS writeout path includes a
> GFP_ATOMIC allocation, in which case this would not suffice.
Bollocks!, GFP_ATOMIC doesn't wait.
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-02-26 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 15:49 [RFC][PATCH] mm: balance_dirty_pages() vs throttle_vm_writeout() deadlock Peter Zijlstra
2007-02-20 20:00 ` Rik van Riel
2007-02-22 0:07 ` Andrew Morton
2007-02-26 13:43 ` Peter Zijlstra
2007-02-26 14:10 ` Peter Zijlstra [this message]
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=1172499051.6374.56.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).