From: firstname.lastname@example.org (bill davidsen)
Subject: Re: Quota Hash Abstraction 2.6.0-test2
Date: 3 Sep 2003 17:23:00 GMT [thread overview]
Message-ID: <email@example.com> (raw)
In article <20030903161435.GC24897@DUK2.13thfloor.at>,
Herbert Poetzl <firstname.lastname@example.org> wrote:
| On Wed, Sep 03, 2003 at 02:56:58PM +0000, bill davidsen wrote:
| > In article <20030731184341.GA21078@www.13thfloor.at>,
| > Herbert =?iso-8859-1?Q?P=F6tzl?= <email@example.com> wrote:
| > Is any of this, particularly the work mentioned in the last paragraph
| > getting into the mail kernel?
| the quota fix was included in the next (test) release
| so default quota will work again ...
Thanks for the quick response, that was my prime concern. I expect to
need quota again in the near future.
| the Quota Hash Abstraction is neither a (big) performance
| gain nor a feature bonus for the end user ... it is more
| an enhancement to the code itself, allowing to have more
| than one quota hash for arbitrary purposes ...
| I doubt, that this code will ever make it into mainline
| without another 'good' reason to use it, but maybe the
| --bind mount quota stuff would be such a reason, if the
| interest for such things will eventually grow ...
Big help, I have never had a performance problem with the quota stuff
other than not performing at all ;-) Good to have the code handy though,
use often follows capability rather than drives it.
bill davidsen <firstname.lastname@example.org>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-09-03 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 18:43 Quota Hash Abstraction 2.6.0-test2 Herbert Pötzl
2003-09-03 14:56 ` bill davidsen
2003-09-03 16:14 ` Herbert Poetzl
2003-09-03 17:23 ` bill davidsen [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).