From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Chris Mason <chris.mason@oracle.com>,
akpm@linux-foundation.org, matthew@wil.cx,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
ngupta@vflare.org, jeremy@goop.org,
Kurt Hackel <kurt.hackel@oracle.com>,
npiggin@kernel.dk, riel@redhat.com,
Konrad Wilk <konrad.wilk@oracle.com>,
mel@csn.ul.ie, minchan.kim@gmail.com
Subject: RE: [PATCH V0 1/4] kztmem: simplified radix tree data structure support
Date: Thu, 16 Dec 2010 21:15:07 -0800 (PST) [thread overview]
Message-ID: <deceffd7-c3a8-49a9-b203-4b4d06af1195@default> (raw)
In-Reply-To: <dd88185d-bc2c-4d65-8730-8b1fc712306a@default>
> A monolithic patch containing all of kztmem, cleancache, and frontswap
> that applies cleanly to 2.6.36 can be found at:
>
> http://oss.oracle.com/projects/tmem/dist/files/kztmem/kztmem-linux-
> 2.6.36-101207.patch
>
> (Or http://oss.oracle.com/projects/tmem and Downloads and kztmem
> patches)
>
> I'm a git novice but can prepare a git tree also if desired.
>
> To try kztmem:
>
> 1) apply the monolithic patch to 2.6.36
> 2) rebuild your config ensuring that CONFIG_KZTMEM, CONFIG_CLEANCACHE,
> CONFIG_FRONTSWAP, and CONFIG_ZRAM (for xvMalloc) become enabled
> 3) rebuild and reboot with "kztmem" as a kernel boot parameter
> 4) see /sys/kernel/mm/kztmem/* for statistics... note that with
> lots of RAM and no swapping, little or no activity will be seen
>
> As I said, there are known weird bugs that may or may not show
> up in your configuration and build environment, so be prepared
> in advance that the kernel may crash... removing kztmem as
> a boot parameter should disable kztmem and result in a normal boot.
>
> Thanks in advance for trying and testing (and, if you are so
> inclined, debugging) kztmem! I'll be happy to answer any
> questions on- or off-list!
FYI, in case anyone was thinking about giving it a spin,
I have just posted an update of the (monolithic) kztmem
patch here:
http://oss.oracle.com/projects/tmem/dist/files/kztmem/kztmem-linux-2.6.36-101207.patch
I think all the weird bugs and crashes are now gone, though I
have some concurrency rework to do after some feedback from
Jeremy Fitzhardinge, and that's not going to happen until
after the holidays. So I am posting this intermediate version
if you want to try it, but please hold off on any detailed
code review until I post v1 to lkml/linux-mm.
Thanks,
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-12-17 5:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 18:06 Dan Magenheimer
2010-12-07 20:43 ` Dan Magenheimer
2010-12-17 5:15 ` 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=deceffd7-c3a8-49a9-b203-4b4d06af1195@default \
--to=dan.magenheimer@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=ngupta@vflare.org \
--cc=npiggin@kernel.dk \
--cc=riel@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