From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jan Kara <jack@suse.cz>, Andreas Dilger <adilger@dilger.ca>,
Aditya Kali <adityakali@google.com>,
"tytso@mit.edu" <tytso@mit.edu>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v2] ext4: make quota as first class supported feature
Date: Sat, 10 Sep 2011 22:24:09 +0200 [thread overview]
Message-ID: <20110910202409.GB6709@quack.suse.cz> (raw)
In-Reply-To: <20110909154057.GA7738@infradead.org>
On Fri 09-09-11 11:40:57, Christoph Hellwig wrote:
> On Mon, Aug 29, 2011 at 10:46:02PM +0200, Jan Kara wrote:
> > The only pain point is repquota(8) - that needs a new kernel interface to
> > work reliably (for ocfs2 and xfs we workaround the inability to iterate
> > over all quota structures from userspace by using getpwent but that's just
> > ugly).
>
> Feel free to a new quotactl case to support it, but I don't reall see
> the problem of the getpwent loop.
Well, the trouble is with systems which have accounts stored e.g. in
LDAP with thousands / tens thousands of users (although each machine is
used only by a small subset of users). Then iterating with getpwent gets
really inefficient...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2011-09-10 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 19:06 [PATCH v2] ext4: make quota as first class supported feature Aditya Kali
2011-08-20 15:58 ` Andreas Dilger
2011-08-21 13:29 ` Dmitry Monakhov
2011-08-22 7:08 ` Aditya Kali
2011-08-29 20:46 ` Jan Kara
2011-09-09 15:40 ` Christoph Hellwig
2011-09-10 20:24 ` Jan Kara [this message]
2011-10-02 14:34 ` Christoph Hellwig
2011-08-29 21:57 ` Jan Kara
2011-08-29 22:42 ` Aditya Kali
2011-08-29 23:17 ` 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=20110910202409.GB6709@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger@dilger.ca \
--cc=adityakali@google.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).