Re: [PATCH] Fix SHMEM options
From: Christoph Hellwig
Date: Fri Nov 12 2004 - 11:51:17 EST
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/