From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-ext4@vger.kernel.org, aneesh.kumar@linux.vnet.ibm.com,
jack@suse.cz, cmm@us.ibm.com, linux-fsdevel@vger.kernel.org,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH 1/3] [RFC] vfs: add generic reserved space management interface
Date: Wed, 09 Dec 2009 17:24:59 +0300 [thread overview]
Message-ID: <877hswql6s.fsf@openvz.org> (raw)
In-Reply-To: <20091209104542.GA10500@infradead.org>
Christoph Hellwig <hch@infradead.org> writes:
> On Wed, Dec 09, 2009 at 05:11:24AM +0300, Dmitry Monakhov wrote:
>> Add new field "i_rsv_blocks" to generic inode. This value is
>> managed similar to i_blocks, i_bytes fileds (protected by i_lock).
>> This generic interface will be used by generic quota code similar
>> to i_blocks.
>
> Please don't bloat the VFS inode for this information.
But almost all recent file systems using extends and delayed allocation.
This means that we have to think about generic space reservation
management quota interface. Otherwise each fs will invent it's own
callbacks. What do you think about hide it with CONFIG_QUOTA option?
May be introduce new CONFIG_QUOTA_RESERVATION?
next prev parent reply other threads:[~2009-12-09 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 2:11 [PATCH 1/3] [RFC] vfs: add generic reserved space management interface Dmitry Monakhov
2009-12-09 2:11 ` [PATCH 2/3] quota: convert to generic reserved space management Dmitry Monakhov
2009-12-09 2:11 ` [PATCH 3/3] ext4: Convert to generic reserved quota's " Dmitry Monakhov
2009-12-10 0:16 ` Mingming
2009-12-10 0:19 ` [PATCH 2/3] quota: convert to generic reserved " Mingming
2009-12-10 1:13 ` Dmitry Monakhov
2009-12-09 10:45 ` [PATCH 1/3] [RFC] vfs: add generic reserved space management interface Christoph Hellwig
2009-12-09 14:24 ` Dmitry Monakhov [this message]
2009-12-09 11:08 ` Jan Kara
2009-12-09 14:51 ` Dmitry Monakhov
2009-12-09 17:00 ` Matthew Wilcox
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=877hswql6s.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.