From: vinayak <vinayakm.list@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
rientjes@google.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: add an option to disable bounce
Date: Mon, 22 Apr 2013 23:07:48 +0530 [thread overview]
Message-ID: <5175756C.5080009@gmail.com> (raw)
In-Reply-To: <51756C24.8060505@infradead.org>
On Monday 22 April 2013 10:28 PM, Randy Dunlap wrote:
> On 04/22/13 08:23, vinayakm.list@gmail.com wrote:
>> From: Vinayak Menon <vinayakm.list@gmail.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@gmail.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)
>> + help
>> + Enable bounce buffers for devices that cannot access
>> + the full range of memory available to the CPU. Enabled
>> + by default when ZONE_DMA or HIGMEM is selected, but you
>
> HIGHMEM
Thanks. I will correct this.
>
>> + may say n to override this.
>>
>> # On the 'tile' arch, USB OHCI needs the bounce pool since tilegx will often
>> # have more than 4GB of memory, but we don't currently use the IOTLB to present
>>
>
>
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-22 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 15:23 [PATCH] mm: add an option to disable bounce vinayakm.list
2013-04-22 16:58 ` Randy Dunlap
2013-04-22 17:37 ` vinayak [this message]
2013-04-22 17:47 ` Russell King - ARM Linux
2013-04-22 18:18 ` vinayak
2013-04-29 20:46 ` KOSAKI Motohiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5175756C.5080009@gmail.com \
--to=vinayakm.list@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).