From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Re: [PATCH] Dynamic lockres hash table
Date: Wed Mar 5 10:42:18 2008 [thread overview]
Message-ID: <47CEE95E.8020200@oracle.com> (raw)
In-Reply-To: <20080305182618.GA10416@duck.suse.cz>
Jan Kara wrote:
> Actually, it's non-trivial to measure (differently than by profiling).
> You cannot use standard time functions because they have too low resolution
> - we are speaking about microseconds here...
>
jiffies should have enough resolution.
> Definitely, they should have 16 or even 32 pages per mount. With 500K
> lockres, which is not so extreme on bigger FS, 16 pages mean hash chains of
> average length 61 on x86_64. It is not ideal but I guess it should be
> sufficient.
>
Any objections to increasing the default to 32 pages for 1.4?
next prev parent reply other threads:[~2008-03-05 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080304102448.GB24335@duck.suse.cz>
2008-03-04 18:33 ` [Ocfs2-devel] Re: [PATCH] Dynamic lockres hash table Sunil Mushran
2008-03-05 10:40 ` Mark Fasheh
2008-03-05 10:47 ` Sunil Mushran
2008-03-05 11:28 ` Joel Becker
2008-03-05 12:39 ` Mark Fasheh
2008-03-05 13:52 ` Joel Becker
2008-03-05 18:26 ` [Ocfs2-devel] " Jan Kara
2008-03-05 10:42 ` Sunil Mushran [this message]
2008-03-06 11:51 ` Jan Kara
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=47CEE95E.8020200@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.