android_kernel_xiaomi_sm8350/arch/v850
Christoph Lameter 0aa817f078 Slab allocators: define common size limitations
Currently we have a maze of configuration variables that determine the
maximum slab size.  Worst of all it seems to vary between SLAB and SLUB.

So define a common maximum size for kmalloc.  For conveniences sake we use
the maximum size ever supported which is 32 MB.  We limit the maximum size
to a lower limit if MAX_ORDER does not allow such large allocations.

For many architectures this patch will have the effect of adding large
kmalloc sizes.  x86_64 adds 5 new kmalloc sizes.  So a small amount of
memory will be needed for these caches (contemporary SLAB has dynamically
sizeable node and cpu structure so the waste is less than in the past)

Most architectures will then be able to allocate object with sizes up to
MAX_ORDER.  We have had repeated breakage (in fact whenever we doubled the
number of supported processors) on IA64 because one or the other struct
grew beyond what the slab allocators supported.  This will avoid future
issues and f.e.  avoid fixes for 2k and 4k cpu support.

CONFIG_LARGE_ALLOCS is no longer necessary so drop it.

It fixes sparc64 with SLAB.

Signed-off-by: Christoph Lameter <clameter@sgi.com>
Signed-off-by: "David S. Miller" <davem@davemloft.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-17 05:23:04 -07:00
..
configs [PATCH] v850: Update defconfigs 2005-09-02 00:57:31 -07:00
kernel Merge git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial 2007-05-09 12:54:17 -07:00
lib [NET]: V850 checksum annotations and cleanups. 2006-12-02 21:23:13 -08:00
Kconfig Slab allocators: define common size limitations 2007-05-17 05:23:04 -07:00
Kconfig.debug
Makefile kbuild: v850 use generic asm-offsets.h support 2005-09-09 21:39:46 +02:00
README [PATCH] v850: Add defconfigs 2005-07-27 16:26:02 -07:00

This port to the NEC V850E processor supports the following platforms:

   "sim"
	The gdb v850e simulator (CONFIG_V850E_SIM).

   "rte-ma1-cb"
	The Midas labs RTE-V850E/MA1-CB and RTE-V850E/NB85E-CB evaluation
	boards (CONFIG_RTE_CB_MA1 and CONFIG_RTE_CB_NB85E).  This support
	has only been tested when running with the Multi-debugger monitor
	ROM (for the Green Hills Multi debugger).  The optional NEC
	Solution Gear RTE-MOTHER-A motherboard is also supported, which
	allows PCI boards to be used (CONFIG_RTE_MB_A_PCI).

   "rte-me2-cb"
	The Midas labs RTE-V850E/ME2-CB evaluation board (CONFIG_RTE_CB_ME2).
     	This has only been tested using a kernel downloaded via an ICE
     	connection using the Multi debugger.  Support for the RTE-MOTHER-A is
     	present, but hasn't been tested (unlike the other Midas labs cpu
     	boards, the RTE-V850E/ME2-CB includes an ethernet adaptor).

   "as85ep1"
	The NEC AS85EP1 V850E evaluation chip/board (CONFIG_V850E_AS85EP1).

   "anna"
	The NEC `Anna' (board/chip) implementation of the V850E2 processor
	(CONFIG_V850E2_ANNA).

   "sim85e2c", "sim85e2s"
   	The sim85e2c and sim85e2s simulators, which are verilog simulations
	of the V850E2 NA85E2C/NA85E2S cpu cores (CONFIG_V850E2_SIM85E2C and
	CONFIG_V850E2_SIM85E2S).

   "fpga85e2c"
	A FPGA implementation of the V850E2 NA85E2C cpu core
	(CONFIG_V850E2_FPGA85E2C).

To get a default kernel configuration for a particular platform, you can
use a <platform>_defconfig make target (e.g., "make rte-me2-cb_defconfig");
to see which default configurations are possible, look in the directory
"arch/v850/configs".

Porting to anything with a V850E/MA1 or MA2 processor should be simple.
See the file <asm-v850/machdep.h> and the files it includes for an example of
how to add platform/chip-specific support.