From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: fengguang.wu@intel.com, mel@csn.ul.ie, npiggin@suse.de,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: what is the point of nr_pages information for the flusher thread?
Date: Wed, 7 Jul 2010 16:55:54 -0700 [thread overview]
Message-ID: <20100707165554.8b898a40.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100707234316.GA21990@infradead.org>
On Wed, 7 Jul 2010 19:43:16 -0400
Christoph Hellwig <hch@infradead.org> wrote:
> > There's also free_more_memory() and do_try_to_free_pages().
>
> Indeed. So we still have some special cases that want a specific
> number to be written back globally.
It could be that those two callsites can be changed to NotDoThat. I do
suggest that you dig through the git record and perhaps the email
archives to work out the thinking - that's old code.
Perhaps we could change things to write back down to the dirty limits,
but that might cause subtle breakage in low-memory situations where
dirty memory is uneven between zones, dunno.
Writing back the whole world would surely be a safe substitute, but
might be inefficient.
I doubt if a whole lot of rigourous thinking went into either one...
--
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>
next prev parent reply other threads:[~2010-07-07 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 23:16 what is the point of nr_pages information for the flusher thread? Christoph Hellwig
2010-07-07 23:16 ` Christoph Hellwig
2010-07-07 23:37 ` Andrew Morton
2010-07-07 23:37 ` Andrew Morton
2010-07-07 23:43 ` Christoph Hellwig
2010-07-07 23:43 ` Christoph Hellwig
2010-07-07 23:55 ` Andrew Morton [this message]
2010-07-10 14:58 ` Wu Fengguang
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=20100707165554.8b898a40.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.de \
/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.