linux-kernel - Re: [PATCH 0/4] ksm - dynamic page sharing driver for linux v3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200904170355.26294.nickpiggin@yahoo.com.au>
Date:	Fri, 17 Apr 2009 03:55:24 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Izik Eidus <ieidus@...hat.com>, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org, linux-mm@...ck.org, avi@...hat.com,
	aarcange@...hat.com, chrisw@...hat.com, mtosatti@...hat.com,
	hugh@...itas.com, kamezawa.hiroyu@...fujitsu.com
Subject: Re: [PATCH 0/4] ksm - dynamic page sharing driver for linux v3

On Wednesday 15 April 2009 08:09:03 Andrew Morton wrote:
> On Thu,  9 Apr 2009 06:58:37 +0300
> Izik Eidus <ieidus@...hat.com> wrote:
> 
> > KSM is a linux driver that allows dynamicly sharing identical memory
> > pages between one or more processes.
> 
> Generally looks OK to me.  But that doesn't mean much.  We should rub
> bottles with words like "hugh" and "nick" on them to be sure.

I haven't looked too closely at it yet sorry. Hugh has a great eye for
these details, though, hint hint :)

As everyone knows, my favourite thing is to say nasty things about any
new feature that adds complexity to common code. I feel like crying to
hear about how many more instances of MS Office we can all run, if only
we apply this patch. And the poorly written HPC app just sounds like
scrapings from the bottom of justification barrel.

I'm sorry, maybe I'm way off with my understanding of how important
this is. There isn't too much help in the changelog. A discussion of
where the memory savings comes from, and how far does things like
sharing of fs image, or ballooning goes and how much extra savings we
get from this... with people from other hypervisors involved as well.
Have I missed this kind of discussion?

Careful what you wish for, ay? :)
--
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/