From: Matt Mackall <mpm@selenic.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nick Piggin <npiggin@suse.de>,
David Howells <dhowells@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: unify shmem and tiny-shmem
Date: Thu, 02 Oct 2008 13:57:26 -0500 [thread overview]
Message-ID: <1222973846.13453.56.camel@calx> (raw)
In-Reply-To: <Pine.LNX.4.64.0810011817060.19654@blonde.site>
On Wed, 2008-10-01 at 19:39 +0100, Hugh Dickins wrote:
> On a different but related subject:
> do you think we need to retain the CONFIG_TMPFS option? It's rather
> odd these days, since everybody gets ramfs, and you give them tmpfs
> via ramfs without CONFIG_SHMEM. If anybody wants to cut out the
> TMPFS code overhead these days, wouldn't they be using !CONFIG_SHMEM?
I agree, it's pretty hard to see a situation where you'd want full
swap-backed shm and not full swap-backed tmpfs. I'll spin up a patch to
follow on my unification.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2008-10-02 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 23:49 [PATCH] mm: unify shmem and tiny-shmem Matt Mackall
2008-10-01 15:00 ` David Howells
2008-10-01 18:39 ` Hugh Dickins
2008-10-02 5:38 ` Nick Piggin
2008-10-02 18:57 ` Matt Mackall [this message]
2008-10-02 22:23 ` David Howells
2008-10-02 22:44 ` Matt Mackall
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=1222973846.13453.56.camel@calx \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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