[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] vmap_pages() (4th resend)
- To: Linus Torvalds <torvalds@transmeta.com>
- Subject: Re: [PATCH] vmap_pages() (4th resend)
- From: Christoph Hellwig <hch@infradead.org>
- Date: Mon, 5 Aug 2002 18:42:57 +0100
- Cc: Christoph Hellwig <hch@lst.de>, linux-mm@kvack.org
- Fake-Sender: owner-linux-mm@kvack.org
- In-Reply-To: <Pine.LNX.4.33.0207291355550.1470-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Mon, Jul 29, 2002 at 01:59:29PM -0700
- Original-Recipient: rfc822;linux-mm-archive@humbolt.geo.uu.nl
- References: <20020729214638.A4582@lst.de> <Pine.LNX.4.33.0207291355550.1470-100000@penguin.transmeta.com>
- Sender: Rik van Riel <riel@nl.linux.org>
- User-Agent: Mutt/1.2.5.1i
On Mon, Jul 29, 2002 at 01:59:29PM -0700, Linus Torvalds wrote:
> Hmm? Is that such a big deal? I think it's worth it for cleanliness, and
> kmalloc() should be plenty big enough (a standard 4kB kmalloc on x86 can
> cover 4MB worth of vmalloc() space, and anybody who wants to vmalloc more
> than than that had better have some good reason for it - and kmalloc()
> does actually work for much larger areas too).
>
> So the kmalloc() approach sounds pretty trivial to me.
It wasn't that trivial, but after the major overhaul I gave to it
mm/vmalloc.c looks much nicer..
Patch will follow shortly.
--
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/