[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1243542908.6645.104.camel@laptop>
Date: Thu, 28 May 2009 22:35:08 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Artem Bityutskiy <dedekind1@...il.com>
Cc: Jens Axboe <jens.axboe@...cle.com>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, tytso@....edu,
chris.mason@...cle.com, david@...morbit.com, hch@...radead.org,
akpm@...ux-foundation.org, jack@...e.cz,
yanmin_zhang@...ux.intel.com, richard@....demon.co.uk,
damien.wyart@...e.fr
Subject: Re: [PATCH 0/11] Per-bdi writeback flusher threads v9
On Thu, 2009-05-28 at 17:19 +0300, Artem Bityutskiy wrote:
> Artem Bityutskiy wrote:
> > question is - should it? 'bdi_register()' a block device,
> > but we do not have one.
>
> Sorry, wanted to say: 'bdi_register()' registers a block
> device.
BDI stands for backing device info and is not related to block devices
other than that block devices can also be (ok, always are) backing
devices.
If you want to do writeback, you need a backing device to write to. The
BDI is the device abstraction for writeback.
--
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/
Powered by blists - more mailing lists