linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Johannes Weiner <jweiner@redhat.com>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Dave Chinner <david@fromorbit.com>,
	xfs@oss.sgi.com, jack@suse.cz, linux-mm@kvack.org
Subject: Re: [PATCH 03/27] xfs: use write_cache_pages for writeback clustering
Date: Fri, 1 Jul 2011 11:15:09 -0400	[thread overview]
Message-ID: <20110701151509.GA30620@infradead.org> (raw)
In-Reply-To: <20110701145935.GB29530@suse.de>

On Fri, Jul 01, 2011 at 03:59:35PM +0100, Mel Gorman wrote:
> On Fri, Jul 01, 2011 at 05:33:05AM -0400, Christoph Hellwig wrote:
> > Johannes, Mel, Wu,
> 
> Am adding Jan Kara as he has been working on writeback efficiency
> recently as well.
> 
> > Dave has been stressing some XFS patches of mine that remove the XFS
> > internal writeback clustering in favour of using write_cache_pages.
> > 
> 
> Against what kernel? 2.6.38 was a disaster for reclaim I've been
> finding out this week. I don't know about 2.6.38.8. 2.6.39 was better.

The patch series is against current 3.0-rc, I assume that's what Dave
tested as well.

> I'm assuming "test 180" is from xfstests which was not one of the tests
> I used previously. To run with 1000 files instead of 100, was the file
> "180" simply editted to make it look like this loop instead?

Yes. to both questions.

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-07-01 15:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110629140109.003209430@bombadil.infradead.org>
     [not found] ` <20110629140336.950805096@bombadil.infradead.org>
     [not found]   ` <20110701022248.GM561@dastard>
     [not found]     ` <20110701041851.GN561@dastard>
2011-07-01  9:33       ` [PATCH 03/27] xfs: use write_cache_pages for writeback clustering Christoph Hellwig
2011-07-01 14:59         ` Mel Gorman
2011-07-01 15:15           ` Christoph Hellwig [this message]
2011-07-02  2:42           ` Dave Chinner
2011-07-05 14:10             ` Mel Gorman
2011-07-05 15:55               ` Dave Chinner
2011-07-11 10:26             ` Christoph Hellwig
2011-07-01 15:41         ` Wu Fengguang
2011-07-04  3:25           ` Dave Chinner
2011-07-05 14:34             ` Mel Gorman
2011-07-06  1:23               ` Dave Chinner
2011-07-11 11:10               ` Christoph Hellwig
2011-07-06  4:53             ` Wu Fengguang
2011-07-06  6:47               ` Minchan Kim
2011-07-06  7:17               ` Dave Chinner
2011-07-06 15:12             ` Johannes Weiner
2011-07-08  9:54               ` Dave Chinner
2011-07-11 17:20                 ` Johannes Weiner
2011-07-11 17:24                   ` Christoph Hellwig
2011-07-11 19:09                   ` Rik van Riel

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=20110701151509.GA30620@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.com \
    --cc=fengguang.wu@intel.com \
    --cc=jack@suse.cz \
    --cc=jweiner@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).