From: David Teigland <teigland@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] dlm patches for 2.6.29 (part 2)
Date: Fri, 9 Jan 2009 15:41:39 -0600 [thread overview]
Message-ID: <1231537301-31459-1-git-send-email-teigland@redhat.com> (raw)
Hi,
Here are two more dlm patches for merging in this cycle.
commit c7be761a8163d2f1ac0b606c21e4316b7abc5af7
Author: David Teigland <teigland@redhat.com>
Date: Wed Jan 7 16:50:41 2009 -0600
dlm: change rsbtbl rwlock to spinlock
The rwlock is almost always used in write mode, so there's no reason
to not use a spinlock instead.
Signed-off-by: David Teigland <teigland@redhat.com>
fs/dlm/debug_fs.c | 24 ++++++++++++------------
fs/dlm/dlm_internal.h | 2 +-
fs/dlm/lock.c | 26 +++++++++++++-------------
fs/dlm/lockspace.c | 2 +-
fs/dlm/recover.c | 10 +++++-----
5 files changed, 32 insertions(+), 32 deletions(-)
commit 892c4467e335e9050c95e0d8409c136c4dadaca2
Author: David Teigland <teigland@redhat.com>
Date: Wed Jan 7 16:48:52 2009 -0600
dlm: fix seq_file usage in debugfs lock dump
The old code would leak iterators and leave reference counts on
rsbs because it was ignoring the "stop" seq callback. The code
followed an example that used the seq operations differently.
This new code is based on actually understanding how the seq
operations work. It also improves things by saving the hash bucket
in the position to avoid cycling through completed buckets in start.
Siged-off-by: Davd Teigland <teigland@redhat.com>
fs/dlm/debug_fs.c | 696 ++++++++++++++++++++++++++---------------------------
1 files changed, 337 insertions(+), 359 deletions(-)
reply other threads:[~2009-01-09 20:56 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=1231537301-31459-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®