All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Andreas Dilger <adilger@sun.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	Jan Kara <jack@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 1/5] vfs: Add additional owner identifier
Date: Fri, 12 Mar 2010 11:47:43 +0300	[thread overview]
Message-ID: <87r5nq9b9s.fsf@openvz.org> (raw)
In-Reply-To: <5010E133-F62A-4F97-AB58-73BF30A347ED@sun.com> (Andreas Dilger's message of "Thu, 11 Mar 2010 12:40:11 -0700")

Andreas Dilger <adilger@sun.com> writes:

> On 2010-03-11, at 11:51, J. Bruce Fields wrote:
>> On Thu, Mar 11, 2010 at 04:11:57PM +0300, Dmitry Monakhov wrote:
>>> Christoph Hellwig <hch@infradead.org> writes:
>>>> There's really no reason to make this a config option.
>>> Project id feature is not likely to be widely used (i hope only
>>> at the beginning). Personally this is not bad to avoid config option.
>>> At least we will have many new users for free. But I predict
>>> many angry voices against enabling this feature by default.
>>
>> How would those "angry voices" notice this feature?
>
>
> The embedded folks are continually complaining about kernel bloat.
>
> I don't see it as a bad thing that there is a config option for a
> feature that will likely be used by < 1% of Linux users.
Definitely we have to hide projectid under kernel config option, bu,t
what option should it be? We have two choices
1) CONFIG_QUOTA: because most of users who use quota probably
   will also use project id support
2) introduce new config option: This may be reasonable if projectid
   may be usefull witout quota and inode size is critical.
   (i dont know such cases for now)
>
> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.

  reply	other threads:[~2010-03-12  8:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 18:34 [PATCH 0/5] RFC: introduce extended inode owner identifier v5 Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 1/5] vfs: Add additional owner identifier Dmitry Monakhov
2010-03-04 18:34   ` [PATCH 2/5] quota: Implement project id support for generic quota Dmitry Monakhov
2010-03-04 18:34     ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2010-03-04 18:34       ` [PATCH 4/5] ext4: add isolated project support Dmitry Monakhov
2010-03-04 18:34         ` [PATCH 5/5] ext4: add project quota support Dmitry Monakhov
2010-03-04 20:07         ` [PATCH 4/5] ext4: add isolated project support Jan Kara
2010-03-04 20:34           ` Dmitry Monakhov
2010-03-11 12:07         ` Christoph Hellwig
2010-03-11 12:06       ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Christoph Hellwig
2010-03-11 13:30         ` Dmitry Monakhov
2010-03-11 19:54           ` Andreas Dilger
2010-03-11 22:01             ` tytso
2010-03-12  9:32               ` Dmitry Monakhov
2010-03-12 20:07                 ` J. Bruce Fields
2010-03-11 12:03     ` [PATCH 2/5] quota: Implement project id support for generic quota Christoph Hellwig
2010-03-11 13:17       ` Dmitry Monakhov
2010-03-11 12:01   ` [PATCH 1/5] vfs: Add additional owner identifier Christoph Hellwig
2010-03-11 13:11     ` Dmitry Monakhov
2010-03-11 18:51       ` J. Bruce Fields
2010-03-11 19:40         ` Andreas Dilger
2010-03-12  8:47           ` Dmitry Monakhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-18 14:02 [PATCH 0/5] RFC: introduce extended inode owner identifier v6 Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 1/5] vfs: Add additional owner identifier Dmitry Monakhov

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=87r5nq9b9s.fsf@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=adilger@sun.com \
    --cc=bfields@fieldses.org \
    --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.