From: Christoph Hellwig <hch@lst.de>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, axboe@kernel.dk, hch@lst.de,
Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: Thinko with per-bdi flusher threads
Date: Fri, 23 Jul 2010 18:58:38 +0200 [thread overview]
Message-ID: <20100723165838.GA24274@lst.de> (raw)
In-Reply-To: <20100723161239.GF3305@quack.suse.cz>
On Fri, Jul 23, 2010 at 06:12:39PM +0200, Jan Kara wrote:
> A reasonable mildly hacky solution would be to file inode against parent
> filesystem's bdi if mapping->backing_dev isn't capable of having dirty
> pages and do writeback and against mapping->backing_dev otherwise. This
> would mean that we would have to properly mark bdis like the one of
> /dev/zero as not capable of writeback.
That seems like a good enough short term solution.
In the long term this should be fixed as a side effect of some patches
I'm about to submit. What I do is to split the writeback code
(bdi_writeback and some fields currently in the backing_dev) off the
backing_dev entirely an make them a separate entity.
mapping->backing_dev will still point to the backing dev, but all inode
dirtying and writeback will be done via the new sb->s_wb.
prev parent reply other threads:[~2010-07-23 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 16:12 Thinko with per-bdi flusher threads Jan Kara
2010-07-23 16:58 ` 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=20100723165838.GA24274@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).