linux-kernel - Re: [PATCH 2/7] writeback: switch to per-bdi threads for flushing data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090316133923.GA27393@infradead.org>
Date:	Mon, 16 Mar 2009 09:39:23 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Chris Mason <chris.mason@...cle.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	david@...morbit.com, npiggin@...e.de, linux-mm@...ck.org
Subject: Re: [PATCH 2/7] writeback: switch to per-bdi threads for flushing
	data

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/