Message-ID: <40010B36.4010306@colorfullife.com>
Date: Sun, 11 Jan 2004 09:37:10 +0100
From: Manfred Spraul <manfred@colorfullife.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030
MIME-Version: 1.0
To: john moser <bluefoxicy@linux.net>
CC: linux-kernel@vger.kernel.org
Subject: Re: krealloc()
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1113
Lines: 29

John Moser wrote:

>I'm not sure if I should just call mmap() inside the
>kernel (any security hazzards or whatnot I should be worried about there?), but
>it's going to be a pain to resize arrays.
>
mmap only works for user space memory, not for kernel memory.

>Most realloc() implimentations grow or shrink in place, if possible.  If they can't,
>or if that wasn't how they were coded, they allocate the new block, memcpy() over,
>then free the old block.
>
>  
>
The kmalloc implementation is object based, it cannot grow in place. The 
only approach is call ksize and check if it fits by chance, otherwise 
alloc new block and memcpy, then free.
Why do you need realloc? What do you want to do? Are you aware that 
kmalloc is limited to 128 kB, and that large kmallocs (I'd guess: > 16 
kB) can fail due to memory fragmentation after long uptimes?

--
    Manfred

-
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/