linux-mips
[Top] [All Lists]

Re: kmalloc issue on MIPS target

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: kmalloc issue on MIPS target
From: naveen yadav <yad.naveen@gmail.com>
Date: Wed, 18 Aug 2010 20:52:11 +0530
Cc: linux-mips@linux-mips.org
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0XZmn4fu07WnVqtWvtz2aQ3MaSUWN6pYO3VGCUp63hE=; b=yIckD3j+LgmUAccT5nqOoV7izZ3aiGEF5cXIhoJFZLdgKJC7JRMlaEL9T9PDA/oDr3 3jE/CNU/xyKmqbkRj1EumMZ32H2L/JVkqcFHc0bKaBckmgVkiUkqE4M+Qink6r6GnGwB 9HxKJaMToydF2y4zOER0P9jpEkvdk31hfVnXU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dPY1o+aSazBqqzPtINm8BQ1SHXtXv/j7R9ixzTZ0p7j7f4fWbTOYtoCEN8pGbGUlwl z7XKPlzptu7UNSfkaoSR244MaOyXzor+DCaO05JULqIdiUx9le2r3juuiGDADFHRoiJV zJ59ZVjw830HHU/z83nUCVcS/y7ECtvQe6gik=
In-reply-to: <20100818144301.GC2849@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <AANLkTiniH42L=-DdJ_XHOm1Uo_=YoAqE-j9Jrm45imtG@mail.gmail.com> <20100818133336.GA25740@linux-mips.org> <AANLkTin8LLH3DkX38B93Ap0mmz4hb9e=cEo9U3ZKmavr@mail.gmail.com> <20100818144301.GC2849@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
Hi Ralf,

I understand that that I need to make kmalloc.h in my arch specific
folder. But I could not get answer, what should be appropriate
value of  ARCH_KMALLOC_MINALIGN  is it 32 or 128 ?


Thanks.

On Wed, Aug 18, 2010 at 8:13 PM, Ralf Baechle <ralf@linux-mips.org> wrote:
> On Wed, Aug 18, 2010 at 07:56:16PM +0530, naveen yadav wrote:
>
>> I will give more info.
>>
>> CONFIG_MIPS_L1_CACHE_SHIFT=5
>>
>> CONFIG_DMA_NONCOHERENT=y
>>
>> mips 34kc is processor
>>
>> and File we are using is  arch/mips/include/asm/mach-generic/kmalloc.h
>>
>> #ifndef __ASM_MACH_GENERIC_KMALLOC_H
>> #define __ASM_MACH_GENERIC_KMALLOC_H
>>
>>
>> #ifndef CONFIG_DMA_COHERENT
>> /*
>>  * Total overkill for most systems but need as a safe default.
>>  * Set this one if any device in the system might do non-coherent DMA.
>>  */
>> #define ARCH_KMALLOC_MINALIGN   128
>> #endif
>>
>> #endif /* __ASM_MACH_GENERIC_KMALLOC_H */
>>
>>
>> So shall we make value ARCH_KMALLOC_MINALIGN   from 128 to 32. is
>> there any problem ?
>
> No, that's just what you should do.  You do that by putting a file
> that defines ARCH_KMALLOC_MINALIGN into your platforms's
> arch/mips/include/asm/mach-<yourplatform>/kmalloc.h just like the ip32
> file from your original posting.
>
>  Ralf
>

<Prev in Thread] Current Thread [Next in Thread>