summaryrefslogtreecommitdiff
path: root/fs/cramfs
diff options
context:
space:
mode:
authorPrzemyslaw Marczak <p.marczak@samsung.com>2015-03-04 14:01:24 +0100
committerTom Rini <trini@konsulko.com>2015-03-09 11:13:28 -0400
commit0aa8a4ad99954ba48c46c31276ec0f6a5f15211d (patch)
tree8dc5c37e0a6ddf873e4012a9c16e76056f794f7e /fs/cramfs
parent41ac233c61af654e86eb980ba02e7e38d05cfcd0 (diff)
downloadu-boot-imx-0aa8a4ad99954ba48c46c31276ec0f6a5f15211d.zip
u-boot-imx-0aa8a4ad99954ba48c46c31276ec0f6a5f15211d.tar.gz
u-boot-imx-0aa8a4ad99954ba48c46c31276ec0f6a5f15211d.tar.bz2
dlmalloc: do memset in malloc init as new default config
This commit introduces new config: CONFIG_SYS_MALLOC_CLEAR_ON_INIT. This config is an expert option and is enabled by default. The all amount of memory reserved for the malloc, is by default set to zero in mem_malloc_init(). When the malloc reserved memory exceeds few MiB, then the boot process can slow down. So disabling this config, is an expert option to reduce the boot time, and can be disabled by Kconfig. Note: After disable this option, only calloc() will return the pointer to the zeroed memory area. Previously, without this option, the memory pointed to untouched malloc memory region, was filled with zeros. So it means, that code with malloc() calls should be reexamined. Signed-off-by: Przemyslaw Marczak <p.marczak@samsung.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'fs/cramfs')
0 files changed, 0 insertions, 0 deletions