From: Chris Mason <mason@suse.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Hans Reiser <reiser@namesys.com>, Oleg Drokin <green@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>,
JPASTORM@esade.edu
Subject: Re: New to reiserfs
Date: 14 May 2002 09:10:46 -0400 [thread overview]
Message-ID: <1021381846.20175.572.camel@tiny> (raw)
In-Reply-To: <200205132324.24309.Dieter.Nuetzel@hamburg.de>
On Mon, 2002-05-13 at 17:24, Dieter Nützel wrote:
> >
> > You should put squid into one big directory (not using their kludge that
> > avoids making directories too large by using a tree)
>
> So you understand me right...;-)
>
> > unless you have multiple processors (in which case the VFS directory giant
> > lock will hurt you).
>
> BKL?
>
> Where is the limit 2, 4, or even more CPUs?
> I'll have two in some days.
You probably want one directory per squid process. The VFS layer does
semaphore locking to prevent races between people reading the directory
and people changing the directory. If you've just got one big
directory, all the squid processes will end up waiting on each other.
More directories mean more time wasted changing the directory stat data,
and ram wasted on reading the stat data. You see this more with
hundreds or thousands of directories.
-chris
next prev parent reply other threads:[~2002-05-14 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 19:53 New to reiserfs Dieter Nützel
2002-05-13 20:02 ` Joe Cooper
2002-05-13 20:57 ` Hans Reiser
2002-05-13 20:57 ` Hans Reiser
2002-05-13 21:24 ` Dieter Nützel
2002-05-14 13:10 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 9:34 JPASTORM
2002-05-13 9:53 ` Oleg Drokin
2002-05-13 10:07 ` Hans Reiser
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=1021381846.20175.572.camel@tiny \
--to=mason@suse.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=JPASTORM@esade.edu \
--cc=green@namesys.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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.