From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
Konrad Wilk <konrad.wilk@oracle.com>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
Andrew Morton <akpm@linux-foundation.org>,
Robert Jennings <rcj@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: RE: [RFC/PATCH] zcache/ramster rewrite and promotion
Date: Mon, 6 Aug 2012 07:07:23 -0700 (PDT) [thread overview]
Message-ID: <f54214e7-cee4-4cbf-aad1-6c1f91867879@default> (raw)
In-Reply-To: <CAOJsxLHe6egmMWdEAGj7DGHHX-hqYMhVWDggny9CsT0H-DOL-g@mail.gmail.com>
> From: Pekka Enberg [mailto:penberg@kernel.org]
> Subject: Re: [RFC/PATCH] zcache/ramster rewrite and promotion
>
> Hi Dan,
>
> On Wed, Aug 1, 2012 at 12:13 AM, Dan Magenheimer
> <dan.magenheimer@oracle.com> wrote:
> > Ramster does the same thing but manages it peer-to-peer across
> > multiple systems using kernel sockets. One could argue that
> > the dependency on sockets makes it more of a driver than "mm"
> > but ramster is "memory management" too, just a bit more exotic.
>
> How do you configure it?
Hi Pekka --
It looks like the build/configuration how-to at
https://oss.oracle.com/projects/tmem/dist/files/RAMster/HOWTO-v5-120214
is out-of-date and I need to fix some things in it. I'll post
a link to it after I update it.
> Can we move parts of the network protocol under
> net/ramster or something?
Ramster is built on top of kernel sockets. Both that networking
part and the configuration part of the ramster code are heavily
leveraged from ocfs2 and I suspect there is a lot of similarity
to gfs code as well. In the code for both of those filesystems
I think the network and configuration code lives in the same
directory with the file system, so that was the model I was following.
I'm OK with placing it wherever kernel developers want to put
it, as long as the reason is not NIMBY-ness. [1] My preference
is to keep all the parts together, at least for the review phase,
but if there is a consensus that it belongs someplace else,
I will be happy to move it.
Dan
[1] http://en.wikipedia.org/wiki/NIMBY
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-08-06 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 20:18 Dan Magenheimer
2012-07-31 20:53 ` Pekka Enberg
2012-07-31 21:04 ` Konrad Rzeszutek Wilk
2012-08-04 8:57 ` Pekka Enberg
2012-07-31 21:13 ` Dan Magenheimer
2012-08-04 8:59 ` Pekka Enberg
2012-08-06 14:07 ` Dan Magenheimer [this message]
2012-08-06 15:44 ` Pekka Enberg
2012-08-06 16:10 ` Dan Magenheimer
2012-08-06 17:13 ` Pekka Enberg
2012-08-07 13:34 ` Dan Magenheimer
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=f54214e7-cee4-4cbf-aad1-6c1f91867879@default \
--to=dan.magenheimer@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@kernel.org \
--cc=rcj@linux.vnet.ibm.com \
--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