[Cluster-devel] [GFS2] Git tree status

2008-06-25 Thread Steven Whitehouse
Hi, I've just been catching up after getting back from holiday. Yesterday I sent to minor bug fixes to Linus, so today I've just updated the -nmw git tree by rebasing to Linus' latest kernel. There are a few patches which I have left in my queue to look at and possibly include in the upcoming

[Cluster-devel] [GFS2] Some patches to clean up lock_dlm etc.

2008-06-25 Thread swhiteho
Hi, Here are some patches which I've collected up in preparation for removal of the lock_dlm module (the plan being to merge it into the main GFS2 module). I've not yet made a decision about whether they will go into this merge window or the next, and that might well depend upon the timing of the

[Cluster-devel] [PATCH] [GFS2] Remove remote lock dropping code

2008-06-25 Thread swhiteho
From: Steven Whitehouse [EMAIL PROTECTED] There are several reasons why this is undesirable: 1. It never happens during normal operation anyway 2. If it does happen it causes performance to be very, very poor 3. It isn't likely to solve the original problem (memory shortage on remote DLM

[Cluster-devel] [PATCH] [GFS2] Remove obsolete conversion deadlock avoidance code

2008-06-25 Thread swhiteho
From: Steven Whitehouse [EMAIL PROTECTED] This is only used by GFS1 so can be removed. Signed-off-by: Steven Whitehouse [EMAIL PROTECTED] diff --git a/fs/gfs2/locking/dlm/lock.c b/fs/gfs2/locking/dlm/lock.c index 871ffc9..894df45 100644 --- a/fs/gfs2/locking/dlm/lock.c +++

[Cluster-devel] [PATCH] [GFS2] Remove all_list from lock_dlm

2008-06-25 Thread swhiteho
From: Steven Whitehouse [EMAIL PROTECTED] I discovered that we had a list onto which every lock_dlm lock was being put. Its only function was to discover whether we'd got any locks left after umount. Since there was already a counter for that purpose as well, I removed the list. The saving is

Re: [Cluster-devel] [GFS2] Some patches to clean up lock_dlm etc.

2008-06-25 Thread Fabio M. Di Nitto
On Wed, 25 Jun 2008, [EMAIL PROTECTED] wrote: Hi, Here are some patches which I've collected up in preparation for removal of the lock_dlm module (the plan being to merge it into the main GFS2 module). I've not yet made a decision about whether they will go into this merge window or the next,

Re: [Cluster-devel] logsys in fenced

2008-06-25 Thread Steven Dake
On Wed, 2008-06-25 at 09:43 -0500, David Teigland wrote: commit 95a5c6b13294742956b13070ebc4f4513278255f Author: Fabio M. Di Nitto [EMAIL PROTECTED] Date: Wed Jun 25 06:24:11 2008 +0200 [FENCE] fenced: separate concept of fork and debugging allow fenced to fork when

Re: [Cluster-devel] logsys in fenced

2008-06-25 Thread Fabio M. Di Nitto
On Wed, 25 Jun 2008, David Teigland wrote: commit 95a5c6b13294742956b13070ebc4f4513278255f Author: Fabio M. Di Nitto [EMAIL PROTECTED] Date: Wed Jun 25 06:24:11 2008 +0200 [FENCE] fenced: separate concept of fork and debugging allow fenced to fork when debugging is set from the

Re: [Cluster-devel] logsys in fenced

2008-06-25 Thread David Teigland
On Wed, Jun 25, 2008 at 06:19:00PM +0200, Fabio M. Di Nitto wrote: . Leave log_debug() unchanged, The only change is that it uses logsys to print instead fprintf to stderr. Like Christine already pointed out, the change to logsys is to have log output the same across the whole system. No