linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux-foundation.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Nick Piggin <npiggin@suse.de>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [rfc] approach to pull writepage out of reclaim
Date: Thu, 09 Oct 2008 15:45:00 -0500	[thread overview]
Message-ID: <48EE6D4C.7080901@linux-foundation.org> (raw)
In-Reply-To: <20081009194434.GB25780@parisc-linux.org>

Matthew Wilcox wrote:
> On Thu, Oct 09, 2008 at 12:06:15PM -0500, Christoph Lameter wrote:
>> Nick Piggin wrote:
>>
>>> So. Firstly, what I'm looking at is doing swap writeout from pdflush. This
>>> patch does that (working in concept, but pdflush and background writeout
>>> from dirty inode list isn't really up to the task, might scrap it and do the
>>> writeout from kswap). But writeout from radix-tree should actually be able to
>>> give better swapout pattern than LRU writepage as well.
>> Patch is missing from the message.
> 
> It's no longer acceptable to post descriptions of what you're about to
> do?  You have to invest lots of time into creating a patch and testing that
> it works before posting it (only to have it shot down because someone
> disagrees with the design of your solution)?  Really?

The text says that a patch was included.... So I was expecting it....

But the problem you mention is real. Tried numerous times to get a conceptual
discussion going without a patch. Usually that does not lead to anything.

--
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>

  reply	other threads:[~2008-10-09 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 14:41 Nick Piggin
2008-10-09 17:06 ` Christoph Lameter
2008-10-09 19:44   ` Matthew Wilcox
2008-10-09 20:45     ` Christoph Lameter [this message]
2008-10-10  2:44       ` Nick Piggin
2008-10-10  7:21 ` KAMEZAWA Hiroyuki
2008-10-11  4:13   ` Nick Piggin

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=48EE6D4C.7080901@linux-foundation.org \
    --to=cl@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew@wil.cx \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox