From: David Teigland <teigland@redhat.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, linux-cluster@redhat.com
Subject: Re: [PATCH 1/3] dlm: use configfs
Date: Fri, 19 Aug 2005 15:13:44 +0800 [thread overview]
Message-ID: <20050819071344.GB10864@redhat.com> (raw)
In-Reply-To: <20050818212348.GW21228@ca-server1.us.oracle.com>
On Thu, Aug 18, 2005 at 02:23:48PM -0700, Mark Fasheh wrote:
> On Thu, Aug 18, 2005 at 02:07:50PM +0800, David Teigland wrote:
> > + * /config/dlm/<cluster>/spaces/<space>/nodes/<node>/nodeid
> > + * /config/dlm/<cluster>/spaces/<space>/nodes/<node>/weight
> > + * /config/dlm/<cluster>/comms/<comm>/nodeid
> > + * /config/dlm/<cluster>/comms/<comm>/local
> > + * /config/dlm/<cluster>/comms/<comm>/addr
>
> So what happened to factoring out the common parts of ocfs2_nodemanager?
> I was quite a big fan of that approach :) Or am I just misunderstanding
> what these patches do?
The nodemanager RFC I sent a month ago
http://marc.theaimsgroup.com/?l=linux-kernel&m=112166723919347&w=2
amounts to half of dlm/config.c (everything under comms/ above) moved into
a separate kernel module. That would be trivial to do, and is still an
option to bat around.
I question whether factoring such a small chunk into a separate module is
really worth it, though? Making all of config.c (all of /config/dlm/
above) into a separate module wouldn't seem quite so strange. It would
require just a few lines of code to turn it into a stand alone module.
Dave
next prev parent reply other threads:[~2005-08-19 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 6:07 [PATCH 1/3] dlm: use configfs David Teigland
2005-08-18 6:22 ` Andrew Morton
[not found] ` <20050818210747.GC22742@insight>
2005-08-20 0:40 ` [Linux-cluster] " Joel Becker
2005-08-18 6:29 ` Nish Aravamudan
2005-08-18 7:12 ` David Teigland
2005-08-18 21:23 ` Mark Fasheh
2005-08-19 7:13 ` David Teigland [this message]
2005-08-23 2:41 ` Mark Fasheh
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=20050819071344.GB10864@redhat.com \
--to=teigland@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-cluster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.