From: Christoph Hellwig <hch@infradead.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <jens.axboe@oracle.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
david@fromorbit.com, npiggin@suse.de, linux-mm@kvack.org
Subject: Re: [PATCH 2/7] writeback: switch to per-bdi threads for flushing data
Date: Mon, 16 Mar 2009 09:39:23 -0400 [thread overview]
Message-ID: <20090316133923.GA27393@infradead.org> (raw)
In-Reply-To: <1237210214.30224.3.camel@think.oraclecorp.com>
On Mon, Mar 16, 2009 at 09:30:14AM -0400, Chris Mason wrote:
> Some of our poor filesystem cousins don't write the super until kupdate
> kicks them (see ext2_write_super). kupdate has always been the periodic
> FS thread of last resort.
Yikes, looks like this is indeed the only peridocial sb update for many
simpler filesystems. We should really have a separate thread for that
instead of hacking it into VM writeback. Especially with the per-bdi
one where the current setup doesn't make any sense.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-03-16 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1236868428-20408-1-git-send-email-jens.axboe@oracle.com>
[not found] ` <1236868428-20408-3-git-send-email-jens.axboe@oracle.com>
2009-03-16 10:22 ` Christoph Hellwig
2009-03-16 13:30 ` Chris Mason
2009-03-16 13:39 ` Christoph Hellwig [this message]
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=20090316133923.GA27393@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=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox