From: Sage Weil <sage@newdream.net>
To: Michal Humpula <michal.humpula@hudrydum.cz>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Quota support
Date: Sun, 23 May 2010 09:14:00 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1005230913420.11676@cobra.newdream.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1005230855200.11676@cobra.newdream.net>
On Sun, 23 May 2010, Sage Weil wrote:
> On Sun, 23 May 2010, Michal Humpula wrote:
> > I was interesting if there is some plan for linux quota support (I've searched
> > the list and the code and found nothing). If it is, is there some experimental
> > code or at least some place with ideas how it should be implemented?
>
> Hi Michal,
>
> Kristal Pollack did a paper on distributed quotas that represents one
> possible approach for enforcement in the case where clients are untrusted:
>
> http://ceph.newdream.net/publications/quota-voucher-paper.pdf
Sorry,
http://ceph.newdream.net/pubs/quota-voucher-paper.pdf
sage
next prev parent reply other threads:[~2010-05-23 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 10:27 Quota support Michal Humpula
2010-05-23 16:00 ` Sage Weil
2010-05-23 16:14 ` Sage Weil [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-07 19:16 quota support Marc Kleine-Budde
[not found] ` <638c4442.362f.15f99519567.Coremail.dongsheng.yang@easystack.cn>
2017-11-08 7:35 ` Marc Kleine-Budde
2017-11-08 9:57 ` Richard Weinberger
2010-06-02 8:57 Quota Support Stephen
2010-06-02 16:01 ` Sean Bartell
2003-12-04 16:04 data logging and quota updated for 2.4.23 Chris Mason
2003-12-08 14:24 ` quota support Bernd Schubert
2003-12-09 11:14 ` Bostjan Skufca (at) domenca.si
2003-12-09 14:38 ` Chris Mason
2003-12-09 16:59 ` Bernd Schubert
2003-12-10 14:03 ` Bostjan Skufca (at) domenca.si
2003-12-10 14:34 ` Bernd Schubert
2003-12-10 19:53 ` Hans Reiser
2003-12-12 15:29 ` 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=Pine.LNX.4.64.1005230913420.11676@cobra.newdream.net \
--to=sage@newdream.net \
--cc=ceph-devel@vger.kernel.org \
--cc=michal.humpula@hudrydum.cz \
/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.