cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 5/5] gfs2: dlm based recovery coordination
Date: Fri, 23 Dec 2011 09:19:39 +0000	[thread overview]
Message-ID: <1324631979.2705.1.camel@menhir> (raw)
In-Reply-To: <20111222212338.GA22571@redhat.com>

Hi,

On Thu, 2011-12-22 at 16:23 -0500, David Teigland wrote:
> On Mon, Dec 19, 2011 at 12:47:38PM -0500, David Teigland wrote:
> > On Mon, Dec 19, 2011 at 01:07:38PM +0000, Steven Whitehouse wrote:
> > > >  struct lm_lockstruct {
> > > >  	int ls_jid;
> > > >  	unsigned int ls_first;
> > > > -	unsigned int ls_first_done;
> > > >  	unsigned int ls_nodir;
> > > Since ls_flags and ls_first also also only boolean flags, they could
> > > potentially be moved into the flags, though we can always do that later.
> > 
> > yes, I can use a flag in place of ls_first.
> 
> I went back to ls_first after finding the flag broke the old code path for
> gfs_controld, and making it work involved changing more of the old code
> that I wanted to in this patch.  We can go back and reorganize how some of
> that old code works (and remove ls_first), in a subsequent patch.
> 
> > > > +	/*
> > > > +	 * Other nodes need to do some work in dlm recovery and gfs2_control
> > > > +	 * before the recover_done and control_lock will be ready for us below.
> > > > +	 * A delay here is not required but often avoids having to retry.
> > > > +	 */
> > > > +
> > > > +	msleep(500);
> 
> This is now msleep_interruptible(500), I couldn't get around adding some
> sort of delay here.  If we think of another way to delay this I'll be
> happy to try it.
> 
> I've finished and tested the rest of the changes.
> https://github.com/teigland/linux-dlm/commits/devel11
> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/teigland/linux-dlm.git;a=shortlog;h=refs/heads/next
> 

Ok. I think we are going very much in the right direction. Let me think
about this over Christmas and lets catch up again in the New Year,

Steve.




  reply	other threads:[~2011-12-23  9:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 22:03 [Cluster-devel] [PATCH 5/5] gfs2: dlm based recovery coordination David Teigland
2011-12-19 13:07 ` Steven Whitehouse
2011-12-19 17:47   ` David Teigland
2011-12-20 10:39     ` Steven Whitehouse
2011-12-20 19:16       ` David Teigland
2011-12-20 21:04         ` David Teigland
2011-12-21 10:45           ` Steven Whitehouse
2011-12-21 15:40             ` David Teigland
2011-12-22 21:23     ` David Teigland
2011-12-23  9:19       ` Steven Whitehouse [this message]
2011-12-19 15:17 ` Steven Whitehouse
2012-01-05 15:08 ` Bob Peterson
2012-01-05 15:21   ` David Teigland
2012-01-05 15:40     ` Steven Whitehouse
2012-01-05 16:16       ` David Teigland
2012-01-05 16:45 ` Bob Peterson
  -- strict thread matches above, loose matches on Subject: below --
2012-01-05 16:46 David Teigland
2012-01-05 16:58 ` Steven Whitehouse
2012-01-05 17:13   ` David Teigland
2012-01-09 16:36 ` Steven Whitehouse
2012-01-09 16:46   ` David Teigland
2012-01-09 17:00     ` David Teigland
2012-01-09 17:04       ` Steven Whitehouse
2012-01-09 17:02     ` Steven Whitehouse

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=1324631979.2705.1.camel@menhir \
    --to=swhiteho@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).