From: "gud" <gud@eth.net>
To: linux-kernel@vger.kernel.org
Subject: Elastic Quota File System (EQFS)
Date: Wed, 23 Jun 2004 21:38:55 +0550 [thread overview]
Message-ID: <40d9ab17.118.0@eth.net> (raw)
Greetings,
I think I should discuss this in the list...
Recently I'm into developing an Elastic Quota File System (EQFS). This
file system works on a simple concept ... give it to others if you're not
using it, let others use it, but on the guarantee that you get it back when
you need it!!
Here I'm talking about disk quotas. In any typical network, e.g.
sourceforge, each user is given a fixed amount of quota. 100 Mb in case of
sourceforge. 100 Mb is way over some project requirements and too small for
some projects. EQFS tries to solve this problem by exploiting the users'
usage behavior at runtime. That is the user's quota which he doesn't need
is given to the users who need it, but on 100% assurance that the originl
user can any time reclaim his/her quota.
Before getting into implementation details I want to have public opinion
about this system. All EQFS tries to do is it maximizes the disk space
usage, which otherwise is wasted if the user doesn't really need the
allocated user..on the other hand it helps avoid the starvation of the user
who needs more space. It also helps administrator to get away with the
problem of variable quota needs..as EQFS itself adjusts according to the
user needs.
regs,
AG
http://www.ddsl.net
next reply other threads:[~2004-06-23 16:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 15:48 gud [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 15:53 Elastic Quota File System (EQFS) Amit Gud
2004-06-23 17:53 ` Mark Watts
[not found] ` <1088016048.15211.10.camel@sage.kitchen>
2004-06-24 9:28 ` Amit Gud
2004-06-24 11:50 ` Olaf Dabrunz
2004-06-24 14:04 ` Sam Elstob
2004-06-24 13:51 ` Olaf Dabrunz
2004-06-24 14:17 ` Pavel Machek
2004-06-24 19:58 ` Fao, Sean
2004-06-24 20:28 ` Timothy Miller
2004-06-24 20:30 ` Timothy Miller
2004-06-24 21:30 ` Pavel Machek
2004-06-24 20:51 ` alan
2004-06-24 22:03 ` Pavel Machek
2004-06-24 23:07 ` alan
2004-06-25 0:15 ` Pavel Machek
2004-06-25 11:57 ` Fao, Sean
2004-06-25 12:07 ` Josh Boyer
2004-06-25 19:34 ` Jörn Engel
2004-06-25 17:37 ` Timothy Miller
2004-06-25 18:44 ` Amit Gud
2004-06-26 12:00 ` Helge Hafting
2004-06-25 19:09 ` Amit Gud
2004-06-30 13:02 ` Olaf Dabrunz
2004-06-25 7:52 ` Lionel Bouton
2004-06-27 18:18 ` V13
2004-06-27 19:42 ` Lionel Bouton
2004-06-28 15:34 ` Amit Gud
2004-06-25 3:04 ` Bernd Eckenfels
2004-06-23 20:37 ` Rik van Riel
2004-06-25 14:02 Amit Gud
2004-06-25 14:23 ` Fao, Sean
2004-06-25 14:44 ` Horst von Brand
2004-06-25 16:25 ` Pavel Machek
2004-06-25 16:44 ` Alan
2004-06-25 17:35 ` Amit Gud
2004-06-25 20:22 ` Fao, Sean
2004-06-25 23:50 ` Kevin Fox
2004-06-26 4:03 ` Amit Gud
2004-06-26 21:36 ` Fao, Sean
2004-06-26 23:16 ` Stephen Wille Padnos
2004-06-27 1:44 ` Fao, Sean
2004-06-28 13:43 ` Rob Couto
2004-06-25 21:36 ` Pavel Machek
2004-06-25 17:07 ` Horst von Brand
2004-06-25 18:44 ` Amit Gud
2004-06-25 21:44 ` Pavel Machek
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=40d9ab17.118.0@eth.net \
--to=gud@eth.net \
--cc=linux-kernel@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