From: Jan Kara <jack@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 00/14] 64-bit quotas and preparations for OCFS2 quotas
Date: Mon, 27 Oct 2008 13:10:19 +0100 [thread overview]
Message-ID: <12251094191314-git-send-email-jack@suse.cz> (raw)
Hello,
the set of patches which will come in following emails implements 64-bit
quotas support and also does some cleanups and necessary changes for quota
support in OCFS2.
64-bit quota support implements new version of quota disk format (which
shares most of the code with current quota format) so quota is no longer
limited by 4 TB space limits and 2^32 inode limit and usage (guys from Sun seem
to have problems with this ;).
OCFS2 quota support needs some changes to the internal quota code since
it treats quota data as filesystem metadata - quota code does not have to
care about problems with accesses to quota files from userspace, but it has
to allow separate enabling of usage accounting and limits enforcement.
Andrew, could you please put these patches to -mm for testing? Thanks.
Eventually, the patches (except for the last one implementing 64-bit quota
format specific functions) are probably going to hit linux-next via ocfs2
git tree but I guess that's not a problem.
Honza
next reply other threads:[~2008-10-27 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 12:10 Jan Kara [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-27 12:11 [PATCH 00/14] 64-bit quotas and preparations for OCFS2 quotas 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=12251094191314-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@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).