From: David Teigland <teigland@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] dlm patches for 3.6
Date: Mon, 23 Jul 2012 13:17:41 -0500 [thread overview]
Message-ID: <1343067467-24308-1-git-send-email-teigland@redhat.com> (raw)
These are the dlm patches from -next for 3.6. The first is a major
internal redesign of the way master nodes are recorded. The old dirtbl
hash table, which just recorded the master node of a resource, has been
removed. The rsbtbl hash table has always duplicated the master value
from dirtbl, but is now the only record of the master node.
Having two full hash tables of all resources has always been inefficient,
especially since one just duplicated information from the other. Requests
that are all local will require one instead of two lengthy hash table
searches.
The other substantial patch is made possible by the dirtbl removal, and
fixes a long standing race between resource removal and lookup by
reworking how removal is done. At the same time it improves the shrink
function efficiency by avoiding repeated searches through hash buckets.
David Teigland (6):
dlm: use rsbtbl as resource directory
dlm: use idr instead of list for recovered rsbs
dlm: fix race between remove and lookup
dlm: use wait_event_timeout
dlm: fix conversion deadlock from recovery
dlm: fix missing dir remove
fs/dlm/config.c | 7 -
fs/dlm/config.h | 1 -
fs/dlm/debug_fs.c | 103 +++-
fs/dlm/dir.c | 287 +++--------
fs/dlm/dir.h | 7 +-
fs/dlm/dlm_internal.h | 62 ++-
fs/dlm/lock.c | 1292 ++++++++++++++++++++++++++++++++++++++++---------
fs/dlm/lock.h | 5 +-
fs/dlm/lockspace.c | 45 +-
fs/dlm/rcom.c | 147 ++++--
fs/dlm/rcom.h | 1 +
fs/dlm/recover.c | 295 +++++++----
fs/dlm/recover.h | 2 +-
fs/dlm/recoverd.c | 14 +-
14 files changed, 1600 insertions(+), 668 deletions(-)
reply other threads:[~2012-07-23 18:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1343067467-24308-1-git-send-email-teigland@redhat.com \
--to=teigland@redhat.com \
--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
all inboxes | Powered by JetHome®