From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Valdis.Kletnieks@vt.edu
Cc: greg@kroah.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
ngupta@vflare.org, Konrad Wilk <konrad.wilk@oracle.com>,
Kurt Hackel <kurt.hackel@oracle.com>,
sjenning@linux.vnet.ibm.com, Chris Mason <chris.mason@oracle.com>
Subject: RE: [PATCH V2 1/6] drivers/staging/ramster: cluster/messaging foundation
Date: Tue, 27 Dec 2011 12:29:46 -0800 (PST) [thread overview]
Message-ID: <7866f872-ce94-4516-bd23-936ea3d0b4e3@default> (raw)
In-Reply-To: <243729.1325016332@turing-police.cc.vt.edu>
> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> Sent: Tuesday, December 27, 2011 1:06 PM
> To: Dan Magenheimer
> Cc: greg@kroah.com; devel@driverdev.osuosl.org; linux-kernel@vger.kernel.org; linux-mm@kvack.org;
> ngupta@vflare.org; Konrad Wilk; Kurt Hackel; sjenning@linux.vnet.ibm.com; Chris Mason
> Subject: Re: [PATCH V2 1/6] drivers/staging/ramster: cluster/messaging foundation
>
> On Thu, 22 Dec 2011 07:50:50 PST, Dan Magenheimer said:
>
> > Copy cluster subdirectory from ocfs2. These files implement
> > the basic cluster discovery, mapping, heartbeat / keepalive, and
> > messaging ("o2net") that ramster requires for internode communication.
>
> Instead of doing this, can we have the shared files copied to a common
> subdirectory so that ramster and ocfs2 can share them, and we only
> have to fix bugs once?
Hi Valdis --
Thanks for your reply!
Per the discussion at:
https://lkml.org/lkml/2011/12/22/369
your suggestion of the common subdirectory will definitely need to happen
before ramster can be promoted out of staging and, at GregKH's request,
I have added a TODO file in V3 to state that. Before that can happen,
we'll need to work with the ocfs2 maintainers to merge the
necessary ramster-specific changes and implement a separately CONFIG-able
subdirectory for the ocfs2 cluster code.
Dan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-12-27 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 15:50 Dan Magenheimer
2011-12-22 17:31 ` Greg KH
2011-12-22 22:06 ` Dan Magenheimer
2011-12-22 22:40 ` Greg KH
2011-12-27 20:34 ` Dan Magenheimer
2011-12-27 20:05 ` Valdis.Kletnieks
2011-12-27 20:29 ` Dan Magenheimer [this message]
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=7866f872-ce94-4516-bd23-936ea3d0b4e3@default \
--to=dan.magenheimer@oracle.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=chris.mason@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=konrad.wilk@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.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