From: Hugh Dickins <hughd@google.com>
To: Ric Mason <ric.masonn@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Petr Holasek <pholasek@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Izik Eidus <izik.eidus@ravellosystems.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/7] ksm: responses to NUMA review
Date: Fri, 22 Feb 2013 12:38:26 -0800 (PST) [thread overview]
Message-ID: <alpine.LNX.2.00.1302221227530.6100@eggly.anvils> (raw)
In-Reply-To: <5126E987.7020809@gmail.com>
On Fri, 22 Feb 2013, Ric Mason wrote:
> On 02/21/2013 04:17 PM, Hugh Dickins wrote:
> > Here's a second KSM series, based on mmotm 2013-02-19-17-20: partly in
> > response to Mel's review feedback, partly fixes to issues that I found
> > myself in doing more review and testing. None of the issues fixed are
> > truly show-stoppers, though I would prefer them fixed sooner than later.
>
> Do you have any ideas ksm support page cache and tmpfs?
No. It's only been asked as a hypothetical question: I don't know of
anyone actually needing it, and I wouldn't have time to do it myself.
It would be significantly more invasive than just dealing with anonymous
memory: with anon, we already have the infrastructure for read-only pages,
but we don't at present have any notion of read-only pagecache.
Just doing it in tmpfs? Well, yes, that might be easier: since v3.1's
radix_tree rework, shmem/tmpfs mostly goes through its own interfaces
to pagecache, so read-only pagecache, and hence KSM, might be easier
to implement there than more generally.
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>
next prev parent reply other threads:[~2013-02-22 20:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 8:17 Hugh Dickins
2013-02-21 8:19 ` [PATCH 1/7] ksm: add some comments Hugh Dickins
2013-02-22 4:26 ` Ric Mason
2013-02-22 20:50 ` Hugh Dickins
2013-02-21 8:20 ` [PATCH 2/7] ksm: treat unstable nid like in stable tree Hugh Dickins
2013-02-22 7:13 ` Ric Mason
2013-02-22 21:03 ` Hugh Dickins
2013-03-01 5:29 ` Ric Mason
2013-03-01 20:03 ` Hugh Dickins
2013-03-02 1:10 ` Ric Mason
2013-03-02 2:57 ` Hugh Dickins
2013-03-06 1:28 ` Will Huck
2013-03-06 4:31 ` Hugh Dickins
2013-03-06 2:37 ` Ric Mason
2013-03-06 5:05 ` Hugh Dickins
2013-03-06 6:58 ` Ric Mason
2013-03-06 10:18 ` Ric Mason
2013-03-07 23:26 ` Ric Mason
2013-02-21 8:22 ` [PATCH 3/7] ksm: shrink 32-bit rmap_item back to 32 bytes Hugh Dickins
2013-02-21 8:23 ` [PATCH 4/7] mm,ksm: FOLL_MIGRATION do migration_entry_wait Hugh Dickins
2013-02-21 8:25 ` [PATCH 5/7] mm,ksm: swapoff might need to copy Hugh Dickins
2013-02-21 14:53 ` Johannes Weiner
2013-02-22 17:16 ` Hugh Dickins
2013-02-21 8:27 ` [PATCH 6/7] mm: cleanup "swapcache" in do_swap_page Hugh Dickins
2013-02-21 8:29 ` [PATCH 7/7] ksm: allocate roots when needed Hugh Dickins
2013-02-22 3:44 ` [PATCH 0/7] ksm: responses to NUMA review Ric Mason
2013-02-22 20:38 ` Hugh Dickins [this message]
2013-02-24 1:39 ` Ric Mason
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=alpine.LNX.2.00.1302221227530.6100@eggly.anvils \
--to=hughd@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=izik.eidus@ravellosystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=pholasek@redhat.com \
--cc=ric.masonn@gmail.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