public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: bzzz@tmi.comex.ru, linux-kernel@vger.kernel.org
Subject: Re: [RFC] parallel directory operations
Date: Tue, 8 Jul 2003 21:26:42 +0200	[thread overview]
Message-ID: <20030708212642.7d7b44ea.ak@suse.de> (raw)
In-Reply-To: <20030708102225.D4482@schatzie.adilger.int>

On Tue, 8 Jul 2003 10:22:25 -0700
Andreas Dilger <adilger@clusterfs.com> wrote:

> On Jul 08, 2003  13:46 +0200, Andi Kleen wrote:
> > On Tue, 08 Jul 2003 15:28:27 +0000 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.
> > 
> > Ok, a mini database lock manager. Wouldn't it be better to use a small hash 
> > table and lock escalation on overflow for this?  Otherwise you could
> > have quite a lot of entries queued up in the list if the server is slow.
> 
> That was my initial thought also, but the number of locks that are in
> existence at one time are very small (i.e. number of threads active in
> a directory at one time).  Having a "more scalable" locking setup will,
> I think, hurt performance for the common case.

I don't see how it will be slower than the current patch.

The main advantage of lock escalation is that the worst case is bounded
very closely (worst it is just like currently with the single lock) 

-Andi

  reply	other threads:[~2003-07-08 19:12 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
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 [this message]
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=20030708212642.7d7b44ea.ak@suse.de \
    --to=ak@suse.de \
    --cc=adilger@clusterfs.com \
    --cc=bzzz@tmi.comex.ru \
    --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