| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 0/6] writeback: tracing and fixes V3. |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 8 Jun 2010 04:03:25 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20100608001115.GB6965@dastard> |
| References: | <1275609328-12514-1-git-send-email-david@xxxxxxxxxxxxx> <20100604074938.GB4448@xxxxxxxxxxxxx> <20100608001115.GB6965@dastard> |
| User-agent: | Mutt/1.5.20 (2009-08-17) |
On Tue, Jun 08, 2010 at 10:11:15AM +1000, Dave Chinner wrote: > On Fri, Jun 04, 2010 at 03:49:38AM -0400, Christoph Hellwig wrote: > > > > Not sure what the rules for new tracepoints are, but in addition to the > > fixes I'd really love to see the tracepoints in 2.6.35. > > Personally I think they are just as important (or even more > important) than the bug fixes because we seem to break this code > regularly because nobody can clearly see what the internals are > doing to verify their change is working correctly. Given that Linus is pretty strict about only taking regression fixes I'd rather get the regression fix in and miss out on the tracing until the next merge window then missing out on everything. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 6/6] writeback: limit write_cache_pages integrity scanning to current EOF, Dave Chinner |
|---|---|
| Next by Date: | Re: xfs, aacraid 2.6.27 => 2.6.32 results in 6 times slowdown, Dave Chinner |
| Previous by Thread: | Re: [PATCH 0/6] writeback: tracing and fixes V3., Dave Chinner |
| Next by Thread: | [GIT] fixes and cleanups for xfs-dev, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |