From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, aneesh.kumar@linux.vnet.ibm.com,
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:51:17 +0300 [thread overview]
Message-ID: <873a3kqjyy.fsf@openvz.org> (raw)
In-Reply-To: <20091209110836.GE4863@quack.suse.de>
Jan Kara <jack@suse.cz> writes:
> On Wed 09-12-09 05:11:24, 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.
> I guess some people won't like bloating the VFS inode. It personally
> makes my "quota" life easier but not that many filesystems need this
> (currently I'm aware of only ext4) so their complaints are reasonable...
Please read my answer to Christoph.
>From other point of view, we may change inode structure like this:
struct quota_ptr
{
struct dquot *dquot[MAXQUOTAS];
};
struct quota_rsv_ptr
{
struct dquot *dquot[MAXQUOTAS];
qsize_t reservation;
};
struct inode {
....
#ifdef CONFIG_QUOTA
union {
struct quota_ptr i_dquot;
struct quota_rsv_ptr i_dquot_rsv;
};
#endif
....
};
Most file systems will use i_dquot, and file systems with reservation
will use quota_rsv_ptr.
Imho this is even better than, macro approach. But this requires
huge patch for each fs, but who cares.
> If we would eventually decide to go this way, I'd account reserved
> space in bytes - quota is really accounted in bytes (as some filesystems
> need this).
Yes you right, I wasn't happy about this too, Will redo.
>
> Honza
next prev parent reply other threads:[~2009-12-09 14:51 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
2009-12-09 11:08 ` Jan Kara
2009-12-09 14:51 ` Dmitry Monakhov [this message]
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=873a3kqjyy.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--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.