linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, Izik Eidus <ieidus@redhat.com>,
	Rik van Riel <riel@redhat.com>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk, device@lanana.org, linux-mm@kvack.org,
	nickpiggin@yahoo.com.au
Subject: Re: [PATCH 3/6] ksm: change the KSM_REMOVE_MEMORY_REGION ioctl.
Date: Thu, 7 May 2009 14:13:31 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0905071339220.12379@blonde.anvils> (raw)
In-Reply-To: <20090507113120.GH16078@random.random>

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

  reply	other threads:[~2009-05-07 13:13 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 22:25 [PATCH 0/6] ksm changes (v2) Izik Eidus
2009-05-04 22:25 ` [PATCH 1/6] ksm: limiting the num of mem regions user can register per fd Izik Eidus
2009-05-04 22:25   ` [PATCH 2/6] ksm: dont allow overlap memory addresses registrations Izik Eidus
2009-05-04 22:25     ` [PATCH 3/6] ksm: change the KSM_REMOVE_MEMORY_REGION ioctl Izik Eidus
2009-05-04 22:25       ` [PATCH 4/6] ksm: change the prot handling to use the generic helper functions Izik Eidus
2009-05-04 22:25         ` [PATCH 5/6] ksm: build system make it compile for all archs Izik Eidus
2009-05-04 22:25           ` [PATCH 6/6] ksm: use another miscdevice minor number Izik Eidus
2009-05-06  0:55             ` Rik van Riel
2009-05-06  0:54           ` [PATCH 5/6] ksm: build system make it compile for all archs Rik van Riel
2009-05-06  0:54         ` [PATCH 4/6] ksm: change the prot handling to use the generic helper functions Rik van Riel
2009-05-06  0:53       ` [PATCH 3/6] ksm: change the KSM_REMOVE_MEMORY_REGION ioctl Rik van Riel
2009-05-06  8:38         ` Izik Eidus
2009-05-06 11:16           ` Hugh Dickins
2009-05-06 13:34             ` Andrea Arcangeli
2009-05-06 13:56               ` Izik Eidus
2009-05-06 16:41                 ` Hugh Dickins
2009-05-06 16:49                   ` Chris Wright
2009-05-06 16:57                     ` Hugh Dickins
2009-05-06 17:47                       ` Andrea Arcangeli
2009-05-06 16:59                     ` Izik Eidus
2009-05-07 11:31                     ` Andrea Arcangeli
2009-05-07 13:13                       ` Hugh Dickins [this message]
2009-05-07 13:23                         ` Andrea Arcangeli
2009-05-06 14:25               ` Hugh Dickins
2009-05-06 14:45                 ` Andrea Arcangeli
2009-05-06 15:36                   ` Chris Wright
2009-05-06 15:27             ` Izik Eidus
2009-05-06 16:14               ` Chris Wright
2009-05-06 16:36                 ` Hugh Dickins
2009-05-06 17:09                   ` Chris Wright
2009-05-06 17:54                     ` Hugh Dickins
2009-05-06 16:26               ` Hugh Dickins
2009-05-06 16:58                 ` Izik Eidus
2009-05-06 23:59                   ` Chris Wright
2009-05-07  2:41                     ` Rik van Riel
2009-05-06  0:43     ` [PATCH 2/6] ksm: dont allow overlap memory addresses registrations Rik van Riel
2009-05-06  9:46       ` Izik Eidus
2009-05-06 12:26         ` Rik van Riel
2009-05-06 12:39           ` Izik Eidus
2009-05-06 13:17           ` Andrea Arcangeli
2009-05-06 13:28             ` Hugh Dickins
2009-05-06 14:02               ` Izik Eidus
2009-05-06 17:11                 ` Hugh Dickins
2009-05-06 14:09               ` Andrea Arcangeli
2009-05-06 14:21                 ` Alan Cox
2009-05-06 14:46                   ` Hugh Dickins
2009-05-06 14:56                     ` Andrea Arcangeli
2009-05-06 23:55                       ` Minchan Kim
2009-05-07  0:19                         ` Chris Wright
2009-05-07 10:46                         ` Andrea Arcangeli
2009-05-07 12:01                           ` Minchan Kim
2009-05-06 14:57                     ` Izik Eidus
2009-05-06  0:40   ` [PATCH 1/6] ksm: limiting the num of mem regions user can register per fd Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2009-05-02 22:16 [PATCH 0/6] ksm changes Izik Eidus
2009-05-02 22:16 ` [PATCH 1/6] ksm: limiting the num of mem regions user can register per fd Izik Eidus
2009-05-02 22:16   ` [PATCH 2/6] ksm: dont allow overlap memory addresses registrations Izik Eidus
2009-05-02 22:16     ` [PATCH 3/6] ksm: change the KSM_REMOVE_MEMORY_REGION ioctl Izik Eidus
2009-05-04 19:43       ` Hugh Dickins
2009-05-04 20:37         ` Izik Eidus

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=Pine.LNX.4.64.0905071339220.12379@blonde.anvils \
    --to=hugh@veritas.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=chrisw@redhat.com \
    --cc=device@lanana.org \
    --cc=ieidus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --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