[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090720154430.GE16361@linux-mips.org>
Date: Mon, 20 Jul 2009 16:44:30 +0100
From: Ralf Baechle <ralf@...ux-mips.org>
To: Izik Eidus <ieidus@...hat.com>
Cc: akpm@...ux-foundation.org, hugh.dickins@...cali.co.uk,
aarcange@...hat.com, chrisw@...hat.com, avi@...hat.com,
riel@...hat.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
nickpiggin@...oo.com.au, Michael Kerrisk <mtk.manpages@...il.com>,
Richard Henderson <rth@...ddle.net>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Kyle McMartin <kyle@...artin.ca>, Helge Deller <deller@....de>,
Chris Zankel <chris@...kel.net>
Subject: Re: [PATCH 03/10] ksm: define MADV_MERGEABLE and MADV_UNMERGEABLE
On Fri, Jul 17, 2009 at 08:30:43PM +0300, Izik Eidus wrote:
> From: Hugh Dickins <hugh.dickins@...cali.co.uk>
>
> The out-of-tree KSM used ioctls on fds cloned from /dev/ksm to register
> a memory area for merging: we prefer now to use an madvise(2) interface.
>
> This patch just defines MADV_MERGEABLE (to tell KSM it may merge pages
> in this area found identical to pages in other mergeable areas) and
> MADV_UNMERGEABLE (to undo that).
>
> Most architectures use asm-generic, but alpha, mips, parisc, xtensa
> need their own definitions: included here for mmotm convenience, but
> we'll probably want to split this and feed pieces to arch maintainers.
I think it's ok to keep these patches combined as a single patch; we'd
normally want them to be applied either all or not at all anyway and if
that's all the arch dependencies KSM has then splitting really just
unnecessarily inflates the number of patches.
Acked-by: Ralf Baechle <ralf@...ux-mips.org>
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists