Date: Fri, 12 Nov 2004 16:45:29 +0000
From: Christoph Hellwig <hch@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, "Martin J. Bligh" <mbligh@aracnet.com>,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix SHMEM options
Message-ID: <20041112164529.GA7308@infradead.org>
Mail-Followup-To: Christoph Hellwig <hch@infradead.org>,
	David Howells <dhowells@redhat.com>, Andrew Morton <akpm@osdl.org>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel@vger.kernel.org
References: <20041111144153.588094d2.akpm@osdl.org> <20041111012333.1b529478.akpm@osdl.org> <20041111030837.12a2090b.akpm@osdl.org> <111920000.1100210158@flay> <20652.1100256658@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20652.1100256658@redhat.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1020
Lines: 25

On Fri, Nov 12, 2004 at 10:50:58AM +0000, David Howells wrote:
> 
> > This change permits CONFIG_SHMEM=n on !CONFIG_MMU, even if !EMBEDDED.  Or
> > something.  I'm not really sure what it's trying to do, nor am I clear on
> > what semantics we wanted to have for CONFIG_SHMEM on CONFIG_MMU machines.
> > 
> > I think the semantics we want are: you always get shmem, unless you
> > selected EMBEDDED.  So perhaps we want:
> 
> It boils down to:
> 
>  (1) You can't use full shmem if !MMU. You have to use tinyshmem instead.
> 
>  (2) On an embedded system, you might want to drop shmem because you don't
>      have much flash in which to store your kernel.
> 
> This seems to have the desired effect:

Note that tiny-shmem really only makes sense for MMU if SWAP is not set.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/