mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: GFS2 Filesystem [15/16]
Date: Mon, 27 Feb 2006 08:52:36 +0000	[thread overview]
Message-ID: <1141030356.6400.786.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20060222185400.GD2633@ucw.cz>

Hi,

On Wed, 2006-02-22 at 18:54 +0000, Pavel Machek wrote:
> > +#include <linux/module.h>
> > +#include <linux/slab.h>
> > +#include <linux/module.h>
> > +#include <linux/init.h>
> > +#include <linux/types.h>
> > +#include <linux/fs.h>
> > +#include <linux/smp_lock.h>
> > +
> > +#include "../../lm_interface.h"
> 
> ugly...
> 
Agreed (see below)

> > +{
> > +	char *c;
> > +	unsigned int jid;
> > +	struct nolock_lockspace *nl;
> > +
> > +	/* If there is a "jid=" in the hostdata, return that jid.
> > +	   Otherwise, return zero. */
> 
> useful comment of the year 2006....
> 
> > +	c = strstr(host_data, "jid=");
> > +	if (!c)
> > +		jid = 0;
> > +	else {
> > +		c += 4;
> > +		sscanf(c, "%u", &jid);
> > +	}
> > +
> 
> ...
> > +
> > +static int nolock_get_lock(lm_lockspace_t *lockspace, struct lm_lockname *name,
> > +			   lm_lock_t **lockp)
> > +{
> > +	*lockp = (lm_lock_t *)lockspace;
> 
> 
> typedef abuse?
> 
The lock module interface has been left identical to that in GFS1 for
the time being so that it is possible to share lock modules between the
two versions. There are a few things which could be tidied up if we were
to change the interface, and we may well do that, but we've been holding
off as long as possible if only to make testing easier.

Since you've brought the subject up, we'll add it to out list :-) Thanks
for the suggestions,

Steve.



  reply	other threads:[~2006-02-27  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 15:07 Steven Whitehouse
2006-02-22 18:54 ` Pavel Machek
2006-02-27  8:52   ` Steven Whitehouse [this message]
2006-02-25 12:06 ` Pekka Enberg

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=1141030356.6400.786.camel@quoit.chygwyn.com \
    --to=swhiteho@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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®