From: Jan Kara <jack@suse.cz>
To: lsf10-pc@lists.linuxfoundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [LSF/VM TOPIC] Writeback code cleanup & improvements
Date: Wed, 24 Feb 2010 15:26:16 +0100 [thread overview]
Message-ID: <20100224142615.GE3687@quack.suse.cz> (raw)
Hi,
here's one suggestion for discussion at LSF/VM summit:
It seems to me that the current writeback code has outlived it's days. The
code is rather complex as various tweaks accumulated over years,
filesystems workaround MAX_WRITEBACK_PAGES limitation to get better
performance, inode writeback is suboptimal for filesystems doing delayed
allocation (we end up writing inodes twice), sync writeback is (at least in
theory) livelockable. So I think it would be worthwhile to sit down and
get to some agreement on how do we improve this situation.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
reply other threads:[~2010-02-24 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100224142615.GE3687@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf10-pc@lists.linuxfoundation.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).