From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [GFS2] default drop count for lock_dlm
Date: Fri, 30 Mar 2007 11:03:28 -0500 [thread overview]
Message-ID: <20070330160327.GA13056@redhat.com> (raw)
In-Reply-To: <1175263091.1636.163.camel@quoit.chygwyn.com>
On Fri, Mar 30, 2007 at 02:58:11PM +0100, Steven Whitehouse wrote:
> Hi,
>
> I think it would be a good plan to have a zero default (i.e. off) for
> the drop_count parameter, otherwise its liable to cause a performance
> problem if its set too low. There is also the question of what exactly
> the "right" setting actually is, as it seems it's not easy to find the
> right balance. Probably the best advice is to only set it in the case
> that the DLM is taking excessive amounts of memory and then use the
> guidance from cat /proc/slabinfo | grep gfs2_glock to get a rough idea
> of the threshold to set it at,
Sounds fine to me.
prev parent reply other threads:[~2007-03-30 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 13:58 [Cluster-devel] [GFS2] default drop count for lock_dlm Steven Whitehouse
2007-03-30 16:03 ` David Teigland [this message]
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=20070330160327.GA13056@redhat.com \
--to=teigland@redhat.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 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).