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]
Date:	Thu, 7 May 2009 14:13:31 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	Andrea Arcangeli <aarcange@...hat.com>
cc:	Chris Wright <chrisw@...hat.com>, Izik Eidus <ieidus@...hat.com>,
	Rik van Riel <riel@...hat.com>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, alan@...rguk.ukuu.org.uk,
	device@...ana.org, linux-mm@...ck.org, nickpiggin@...oo.com.au
Subject: Re: [PATCH 3/6] ksm: change the KSM_REMOVE_MEMORY_REGION ioctl.

On Thu, 7 May 2009, Andrea Arcangeli wrote:
> 
> What this thing does is to create shared pages by merging equal pages...
> 
> While I don't care about the naming much myself, one problem I have is
> that I've been writing a KSM paper for linuxsymposium and I'd like to
> use a nomenclature that is in sync with how this stuff should be
> called on lkml, to avoid confusion.

Sorry for sparking this namechange at such a late date,
inflicting such nuisance upon you.

> 
> So should I change the simpler word KSM with "Memory Merging feature"
> all over the paper?

No: "KSM" stands for "Kernel Samepage Merging", doesn't it?
Or maybe someone can devise a better term for the "S" of it.

I think we're all too familiar with "KSM" to want to outlaw that,
just don't dwell too much on the "Kernel Shared Memory" expansion.

> 
> In addition I consistently use the term "shared KSM pages" often,
> should I rename all those instances to "merged pages"? I used the word
> 'merging' only when describing the operation KSM does when it creates
> shared pages, but never to name the generated pages themself.

No, you and your audience and your readers will find it clearest
if you remark on the change in naming upfront, then get on with
describing it all in the way that comes most naturally to you.

But do sprinkle in a few "merged pages", I suggest: perhaps by
the time you deliver it, they'll be coming more naturally to you.

(Actually, "shared KSM pages" makes more sense if that "S" is not
for Shared.  I keep wondering what the two "k"s in kksmd stand for.)

Hugh
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ