All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	chris.mason@oracle.com, david@fromorbit.com, npiggin@suse.de
Subject: Re: [PATCH 3/7] writeback: get rid of pdflush_operation() in emergency sync and remount
Date: Mon, 16 Mar 2009 06:13:43 -0400	[thread overview]
Message-ID: <20090316101343.GA21118@infradead.org> (raw)
In-Reply-To: <1236868428-20408-4-git-send-email-jens.axboe@oracle.com>

On Thu, Mar 12, 2009 at 03:33:44PM +0100, Jens Axboe wrote:
> Opencode a cheasy approach with kevent. The idea here is that we'll
> add some generic delayed work infrastructure, which probably wont be
> based on pdflush (or maybe it will, in which case we can just add it
> back).

Good idea.  Care to submit this early outside of the series?

> 

  reply	other threads:[~2009-03-16 10:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 14:33 [PATCH 0/7] Per-bdi writeback flusher threads Jens Axboe
2009-03-12 14:33 ` [PATCH 1/7] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-03-24 16:17   ` Jan Kara
2009-03-24 18:45     ` Jens Axboe
2009-03-12 14:33 ` [PATCH 2/7] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-03-13  5:33   ` Andrew Morton
2009-03-13 10:54     ` Jens Axboe
2009-03-15 22:52       ` Dave Chinner
2009-03-16  7:33         ` Jens Axboe
2009-03-16 10:17           ` Christoph Hellwig
2009-03-16 10:21             ` Jens Axboe
2009-03-16 23:38           ` Dave Chinner
2009-03-17  9:37             ` Jens Axboe
2009-03-17 13:21             ` Chris Mason
2009-03-16 10:22   ` Christoph Hellwig
2009-03-16 10:22     ` Christoph Hellwig
2009-03-16 13:30     ` Chris Mason
2009-03-16 13:30       ` Chris Mason
2009-03-16 13:39       ` Christoph Hellwig
2009-03-16 13:39         ` Christoph Hellwig
2009-03-12 14:33 ` [PATCH 3/7] writeback: get rid of pdflush_operation() in emergency sync and remount Jens Axboe
2009-03-16 10:13   ` Christoph Hellwig [this message]
2009-03-12 14:33 ` [PATCH 4/7] writeback: get rid of task/current_is_pdflush() Jens Axboe
2009-03-16 10:14   ` Christoph Hellwig
2009-03-16 10:22     ` Jens Axboe
2009-03-16 13:26     ` Chris Mason
2009-03-12 14:33 ` [PATCH 5/7] writeback: move the default backing_dev_info out of readahead Jens Axboe
2009-03-16 10:19   ` Christoph Hellwig
2009-03-16 10:23     ` Jens Axboe
2009-03-12 14:33 ` [PATCH 6/7] writeback: add lazy bdi->task creation Jens Axboe
2009-03-12 14:33 ` [PATCH 7/7] writeback: add some debug inode list counters to bdi stats 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=20090316101343.GA21118@infradead.org \
    --to=hch@infradead.org \
    --cc=chris.mason@oracle.com \
    --cc=david@fromorbit.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    /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.