[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51757F0B.1090104@gmail.com>
Date: Mon, 22 Apr 2013 23:48:51 +0530
From: vinayak <vinayakm.list@...il.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
CC: linux-mm@...ck.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
rientjes@...gle.com
Subject: Re: [PATCH] mm: add an option to disable bounce
On Monday 22 April 2013 11:17 PM, Russell King - ARM Linux wrote:
> On Mon, Apr 22, 2013 at 08:53:00PM +0530, vinayakm.list@...il.com wrote:
>> From: Vinayak Menon <vinayakm.list@...il.com>
>>
>> There are times when HIGHMEM is enabled, but
>> we don't prefer CONFIG_BOUNCE to be enabled.
>> CONFIG_BOUNCE can reduce the block device
>> throughput, and this is not ideal for machines
>> where we don't gain much by enabling it. So
>> provide an option to deselect CONFIG_BOUNCE. The
>> observation was made while measuring eMMC throughput
>> using iozone on an ARM device with 1GB RAM.
>>
>> Signed-off-by: Vinayak Menon <vinayakm.list@...il.com>
>> ---
>> mm/Kconfig | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/mm/Kconfig b/mm/Kconfig
>> index 3bea74f..29f9736 100644
>> --- a/mm/Kconfig
>> +++ b/mm/Kconfig
>> @@ -263,8 +263,14 @@ config ZONE_DMA_FLAG
>> default "1"
>>
>> config BOUNCE
>> + bool "Enable bounce buffers"
>> def_bool y
>> depends on BLOCK && MMU && (ZONE_DMA || HIGHMEM)
>
> I don't think this is correct. You shouldn't use "bool" with "def_bool".
> Sure, add the "bool", but also change "def_bool" to "default".
Yes. I will change it to "default" and this looks to be correct
even from the definition in kconfig-language.txt. But I see other
instances in mm/Kconfig, where bool and def_bool are used together. When
I had tested this patch with def_bool, it worked as expected.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists