From: bzzz@tmi.comex.ru
To: Andi Kleen <ak@suse.de>
Cc: bzzz@tmi.comex.ru, linux-kernel@vger.kernel.org
Subject: Re: [RFC] parallel directory operations
Date: Tue, 08 Jul 2003 15:50:27 +0000 [thread overview]
Message-ID: <87fzlhuif0.fsf@gw.home.net> (raw)
In-Reply-To: <20030708134601.7992e64a.ak@suse.de> (Andi Kleen's message of "Tue, 8 Jul 2003 13:46:01 +0200")
>>>>> Andi Kleen (AK) writes:
AK> On Tue, 08 Jul 2003 15:28:27 +0000
AK> bzzz@tmi.comex.ru wrote:
>> dynlocks implements 'lock namespace', so you can lock A for namepace N1 and
>> lock B for namespace N1 and so on. we need this because we want to take lock
>> on _part_ of directory.
AK> Ok, a mini database lock manager. Wouldn't it be better to use a small hash
AK> table and lock escalation on overflow for this? Otherwise you could
AK> have quite a lot of entries queued up in the list if the server is slow.
well, it makes sense. AFAIU, only problem with this solution is that we need
very well-tuned hash function. BTW, dynlocks are taken for operation time only.
so, in most often case, for dir entry creation/lookup we need two locks: one for
dcache locking and another for htree's leaf locking.
next prev parent reply other threads:[~2003-07-08 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wuetukpa.fsf@gw.home.net.suse.lists.linux.kernel>
2003-07-08 11:26 ` [RFC] parallel directory operations Andi Kleen
2003-07-08 15:28 ` bzzz
2003-07-08 11:46 ` Andi Kleen
2003-07-08 15:50 ` bzzz [this message]
2003-07-08 12:11 ` Andi Kleen
2003-07-08 16:17 ` Alex Tomas
2003-07-08 13:11 ` Nikita Danilov
2003-07-08 17:15 ` bzzz
2003-07-08 13:29 ` Nikita Danilov
2003-07-08 17:38 ` Alex Tomas
2003-07-08 17:22 ` Andreas Dilger
2003-07-08 19:26 ` Andi Kleen
2003-07-08 15:01 Alex Tomas
-- strict thread matches above, loose matches on Subject: below --
2005-02-19 17:57 Alex Tomas
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=87fzlhuif0.fsf@gw.home.net \
--to=bzzz@tmi.comex.ru \
--cc=ak@suse.de \
--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 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.