linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: linux-ext4@vger.kernel.org
Subject: RFC Per group orphan list
Date: Wed, 28 Apr 2010 14:55:29 +0400	[thread overview]
Message-ID: <87och3q21q.fsf@openvz.org> (raw)

Currently orphan list is global, which require per-sb mutex
to protect add/del from the list. But it is not really necessary.
Just think about it we have to add inode to orphan list for each
->write_begin call(for each page) if i_size will grow.
For example btrfs support per-ctree orphan list.
So IMHO per-group orphan list seems to be more natural here.
So my proposal is following:
1) Introduce new incompat feature for per-group orphan list. 
2) Store per-group head of the list in group descriptor
   (Where are several reserved fields in grp-desc).
3) Maintain per-group orphan which protected by per-group lst-mutex. 
4) Let fsck to scan group descriptors after unclean umount.Since they
   are close to each other performance penalty will be negligible.

Seems that development complexity of this feature is not too high, 
what do you think.

             reply	other threads:[~2010-04-28 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 10:55 Dmitry Monakhov [this message]
2010-04-28 22:17 ` RFC Per group orphan list Jan Kara

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=87och3q21q.fsf@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=linux-ext4@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).