From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] DLM thoughts - multi threaded recvd
Date: Wed, 20 Dec 2006 09:53:53 -0600 [thread overview]
Message-ID: <20061220155353.GA8787@redhat.com> (raw)
In-Reply-To: <45895059.9030506@redhat.com>
On Wed, Dec 20, 2006 at 03:01:45PM +0000, Patrick Caulfield wrote:
> One of the things that Andrew Morton commented on when taking the DLM
> was that that there is a single dlm_recvd process (and sendd too)
> processing incoming requests and it could become a bottleneck on large
> systems.
Yes, dlm_recvd does quite a bit of work per message, I could see a backlog
as a real possibility. Whether there are very dire effects of that I'm
not sure.
>
> So, I've been thinking how to make this scale a little better and have
> come up with several things.
>
> 1. How do we decide how many threads to start?
I think we just pick a default number that will work well for most use
cases, probably something like 2, and then allow it to be configured. Or,
create one or two threads per lockspace.
prev parent reply other threads:[~2006-12-20 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 15:01 [Cluster-devel] DLM thoughts - multi threaded recvd Patrick Caulfield
2006-12-20 15:41 ` Steven Whitehouse
2006-12-21 11:57 ` Patrick Caulfield
2006-12-20 15:53 ` 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=20061220155353.GA8787@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 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.