All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	xfs@oss.sgi.com
Subject: Re: [PATCH 0/6] writeback: tracing and fixes V4
Date: Tue, 8 Jun 2010 15:44:46 +1000	[thread overview]
Message-ID: <20100608054446.GT26335@laptop> (raw)
In-Reply-To: <1275957487-23633-1-git-send-email-david@fromorbit.com>

On Tue, Jun 08, 2010 at 10:38:01AM +1000, Dave Chinner wrote:
> Hi Linus,
> 
> Can you please consider this patch series for 2.6.35? If you don't
> want the tracing at this stage of the release process, I can redo
> the series with just the bug fixes. However, given the regularity
> with which we break the writeback code in subtle ways, the tracing
> is probably just as important as the bug fixes.

Oh, I don't have a problem with your EOF fix being merged now, as Jan's
patch isn't suitable for 2.6.35.

_______________________________________________
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: Dave Chinner <david@fromorbit.com>
Cc: torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH 0/6] writeback: tracing and fixes V4
Date: Tue, 8 Jun 2010 15:44:46 +1000	[thread overview]
Message-ID: <20100608054446.GT26335@laptop> (raw)
In-Reply-To: <1275957487-23633-1-git-send-email-david@fromorbit.com>

On Tue, Jun 08, 2010 at 10:38:01AM +1000, Dave Chinner wrote:
> Hi Linus,
> 
> Can you please consider this patch series for 2.6.35? If you don't
> want the tracing at this stage of the release process, I can redo
> the series with just the bug fixes. However, given the regularity
> with which we break the writeback code in subtle ways, the tracing
> is probably just as important as the bug fixes.

Oh, I don't have a problem with your EOF fix being merged now, as Jan's
patch isn't suitable for 2.6.35.


  parent reply	other threads:[~2010-06-08  5:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08  0:38 [PATCH 0/6] writeback: tracing and fixes V4 Dave Chinner
2010-06-08  0:38 ` Dave Chinner
2010-06-08  0:38 ` [PATCH 1/6] writeback: initial tracing support Dave Chinner
2010-06-08  0:38   ` Dave Chinner
2010-06-08  0:38 ` [PATCH 2/6] writeback: Add tracing to balance_dirty_pages Dave Chinner
2010-06-08  0:38   ` Dave Chinner
2010-06-08  0:38 ` [PATCH 3/6] writeback: Add tracing to write_cache_pages Dave Chinner
2010-06-08  0:38   ` Dave Chinner
2010-06-08  0:38 ` [PATCH 4/6] writeback: pay attention to wbc->nr_to_write in write_cache_pages Dave Chinner
2010-06-08  0:38   ` Dave Chinner
2010-06-08  5:43   ` Nick Piggin
2010-06-08  5:43     ` Nick Piggin
2010-06-08  0:38 ` [PATCH 5/6] xfs: remove nr_to_write writeback windup Dave Chinner
2010-06-08  0:38   ` 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-06-08  5:44 ` Nick Piggin [this message]
2010-06-08  5:44   ` [PATCH 0/6] writeback: tracing and fixes V4 Nick Piggin
2010-06-08 17:41 ` Linus Torvalds
2010-06-08 17:41   ` Linus Torvalds
2010-06-08 17:50   ` Andrew Morton
2010-06-08 17:50     ` Andrew Morton
2010-06-08 22:46   ` Dave Chinner
2010-06-08 22:46     ` Dave Chinner

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=20100608054446.GT26335@laptop \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.