From: Nick Piggin <npiggin@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 6/6] writeback: limit write_cache_pages integrity scanning to current EOF
Date: Fri, 4 Jun 2010 17:56:14 +1000 [thread overview]
Message-ID: <20100604075614.GB26335@laptop> (raw)
In-Reply-To: <20100604075223.GB7317@infradead.org>
On Fri, Jun 04, 2010 at 03:52:23AM -0400, Christoph Hellwig wrote:
> Even if there still are potential livelocks after this it's a big
> step in the right direction, so
>
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Agreed.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com, akpm@linux-foundation.org
Subject: Re: [PATCH 6/6] writeback: limit write_cache_pages integrity scanning to current EOF
Date: Fri, 4 Jun 2010 17:56:14 +1000 [thread overview]
Message-ID: <20100604075614.GB26335@laptop> (raw)
In-Reply-To: <20100604075223.GB7317@infradead.org>
On Fri, Jun 04, 2010 at 03:52:23AM -0400, Christoph Hellwig wrote:
> Even if there still are potential livelocks after this it's a big
> step in the right direction, so
>
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Agreed.
next prev parent reply other threads:[~2010-06-04 7:53 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 23:55 [PATCH 0/6] writeback: tracing and fixes V3 Dave Chinner
2010-06-03 23:55 ` Dave Chinner
2010-06-03 23:55 ` [PATCH 1/6] writeback: initial tracing support Dave Chinner
2010-06-03 23:55 ` Dave Chinner
2010-06-04 1:10 ` Li Zefan
2010-06-04 1:10 ` Li Zefan
2010-06-04 1:24 ` Dave Chinner
2010-06-04 1:24 ` Dave Chinner
2010-06-03 23:55 ` [PATCH 2/6] writeback: Add tracing to balance_dirty_pages Dave Chinner
2010-06-03 23:55 ` Dave Chinner
2010-06-03 23:55 ` [PATCH 3/6] writeback: Add tracing to write_cache_pages Dave Chinner
2010-06-03 23:55 ` Dave Chinner
2010-06-04 7:51 ` Christoph Hellwig
2010-06-04 7:51 ` Christoph Hellwig
2010-06-03 23:55 ` [PATCH 4/6] writeback: pay attention to wbc->nr_to_write in write_cache_pages Dave Chinner
2010-06-03 23:55 ` Dave Chinner
2010-06-04 7:48 ` Christoph Hellwig
2010-06-04 7:48 ` Christoph Hellwig
2010-06-03 23:55 ` [PATCH 5/6] xfs: remove nr_to_write writeback windup Dave Chinner
2010-06-03 23:55 ` Dave Chinner
2010-06-03 23:55 ` [PATCH 6/6] writeback: limit write_cache_pages integrity scanning to current EOF Dave Chinner
2010-06-03 23:55 ` Dave Chinner
2010-06-04 7:52 ` Christoph Hellwig
2010-06-04 7:52 ` Christoph Hellwig
2010-06-04 7:56 ` Nick Piggin [this message]
2010-06-04 7:56 ` Nick Piggin
2010-06-04 7:49 ` [PATCH 0/6] writeback: tracing and fixes V3 Christoph Hellwig
2010-06-04 7:49 ` Christoph Hellwig
2010-06-08 0:11 ` Dave Chinner
2010-06-08 0:11 ` Dave Chinner
2010-06-08 8:03 ` Christoph Hellwig
2010-06-08 8:03 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2010-06-08 0:38 [PATCH 0/6] writeback: tracing and fixes V4 Dave Chinner
2010-06-08 0:38 ` [PATCH 6/6] writeback: limit write_cache_pages integrity scanning to current EOF Dave Chinner
2010-06-08 0:38 ` Dave Chinner
2010-06-08 5:38 ` Nick Piggin
2010-06-08 5:38 ` Nick Piggin
2010-06-08 6:59 ` Dave Chinner
2010-06-08 6:59 ` Dave Chinner
2010-05-25 10:54 [PATCH 0/6] writeback: tracing and fixes Dave Chinner
2010-05-25 10:54 ` [PATCH 6/6] writeback: limit write_cache_pages integrity scanning to current EOF Dave Chinner
2010-05-25 10:54 ` Dave Chinner
2010-05-27 21:33 ` Andrew Morton
2010-05-27 21:33 ` Andrew Morton
2010-05-28 1:23 ` Dave Chinner
2010-05-28 1:23 ` Dave Chinner
2010-05-28 5:06 ` Nick Piggin
2010-05-28 5:06 ` Nick Piggin
2010-06-01 15:54 ` Jan Kara
2010-06-01 15:54 ` Jan Kara
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=20100604075614.GB26335@laptop \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.