From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755166AbYJBTB1 (ORCPT ); Thu, 2 Oct 2008 15:01:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754080AbYJBTBS (ORCPT ); Thu, 2 Oct 2008 15:01:18 -0400 Received: from waste.org ([66.93.16.53]:49514 "EHLO waste.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753932AbYJBTBS (ORCPT ); Thu, 2 Oct 2008 15:01:18 -0400 Subject: Re: [PATCH] mm: unify shmem and tiny-shmem From: Matt Mackall To: Hugh Dickins Cc: Nick Piggin , David Howells , Linux Kernel Mailing List , Andrew Morton In-Reply-To: References: <1222818570.13453.5.camel@calx> Content-Type: text/plain Date: Thu, 02 Oct 2008 13:57:26 -0500 Message-Id: <1222973846.13453.56.camel@calx> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.