From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
chris.mason@oracle.com, david@fromorbit.com,
akpm@linux-foundation.org, jack@suse.cz
Subject: Re: [PATCH 0/7] Per-bdi writeback flusher threads v15
Date: Mon, 31 Aug 2009 21:56:02 +0200 [thread overview]
Message-ID: <20090831195602.GB12579@kernel.dk> (raw)
In-Reply-To: <20090831195148.GA26130@infradead.org>
On Mon, Aug 31 2009, Christoph Hellwig wrote:
> On Mon, Aug 31, 2009 at 09:41:26PM +0200, Jens Axboe wrote:
> > Christoph, let me know if there are things you are still not happy
> > with and I will reply/address them. Note that this series has only
> > received a light testing. This means that it boots and seems to work
> > (flushes data on sync and at intervals) and does not corrupt data,
> > but it hasn't received a thorough testing yet. That will come tomorrow.
> > But I wanted to push this out there, so we can settle the code base
> > quickly again.
>
> I'll slowly look over it later. But I think it would be extremly
> helpful if we could get it into -next ASAP for wider testing.
Yeah, will update my for-next branch. It _should_ be functionally
equivalent to the previous posting which has recieved a LOT of testing,
but there can be new bugs of course. So far it still seems fine, so
should be safe...
--
Jens Axboe
next prev parent reply other threads:[~2009-08-31 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 19:41 [PATCH 0/7] Per-bdi writeback flusher threads v15 Jens Axboe
2009-08-31 19:41 ` [PATCH 1/7] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-08-31 19:41 ` [PATCH 2/7] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-08-31 19:41 ` [PATCH 3/7] writeback: get rid of pdflush completely Jens Axboe
2009-08-31 19:41 ` [PATCH 4/7] writeback: add some debug inode list counters to bdi stats Jens Axboe
2009-08-31 19:41 ` [PATCH 5/7] writeback: add name to backing_dev_info Jens Axboe
2009-08-31 19:41 ` [PATCH 6/7] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe
2009-08-31 19:41 ` [PATCH 7/7] vm: Add an tuning knob for vm.max_writeback_pages Jens Axboe
2009-08-31 19:51 ` [PATCH 0/7] Per-bdi writeback flusher threads v15 Christoph Hellwig
2009-08-31 19:56 ` Jens Axboe [this message]
2009-08-31 19:56 ` Jens Axboe
2009-09-01 4:01 ` Theodore Tso
2009-09-01 6:29 ` Jens Axboe
2009-09-01 7:24 ` Jens Axboe
2009-09-01 7:46 ` Jens Axboe
2009-09-01 8:06 ` Jens Axboe
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=20090831195602.GB12579@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.