Home
last modified time | relevance | path

Searched refs:madvise (Results 1 – 18 of 18) sorted by relevance

/linux-4.1.27/tools/testing/selftests/vm/
Dtranshuge-stress.c40 if (madvise(ptr, HPAGE_SIZE, MADV_HUGEPAGE)) in allocate_transhuge()
95 if (madvise(ptr, len, MADV_HUGEPAGE)) in main()
133 if (madvise(p, HPAGE_SIZE - PAGE_SIZE, MADV_DONTNEED)) in main()
/linux-4.1.27/Documentation/vm/
Dksm.txt24 has advised to be likely candidates for merging, by using the madvise(2)
25 system call: int madvise(addr, length, MADV_MERGEABLE).
27 The app may call int madvise(addr, length, MADV_UNMERGEABLE) to cancel
33 If KSM is not configured into the running kernel, madvise MADV_MERGEABLE
41 Like other madvise calls, they are intended for use on mapped areas of
94 proportion there would also indicate poor use of madvise MADV_MERGEABLE.
Dtranshuge.txt85 MADV_HUGEPAGE madvise regions.
87 Embedded systems should enable hugepages only inside madvise regions
93 madvise(MADV_HUGEPAGE) on their critical mmapped regions.
103 echo madvise >/sys/kernel/mm/transparent_hugepage/enabled
107 hugepages in case they're not immediately free to madvise regions or
116 echo madvise >/sys/kernel/mm/transparent_hugepage/defrag
127 transparent_hugepage/enabled is set to "always" or "madvise, and it'll
177 "transparent_hugepage=madvise" or "transparent_hugepage=never"
Dhwpoison.txt100 madvise(MADV_HWPOISON, ....)
/linux-4.1.27/arch/um/os-Linux/
Dprocess.c177 err = madvise(addr, length, MADV_REMOVE); in os_drop_memory()
204 if (madvise(addr, UM_KERN_PAGE_SIZE, MADV_REMOVE) != 0) { in can_drop_memory()
/linux-4.1.27/mm/
DMakefile36 obj-$(CONFIG_ADVISE_SYSCALLS) += madvise.o
Dmadvise.c458 SYSCALL_DEFINE3(madvise, unsigned long, start, size_t, len_in, int, behavior) in SYSCALL_DEFINE3() argument
DKconfig439 bool "madvise"
441 Enabling Transparent Hugepage madvise, will only provide a
443 madvise(MADV_HUGEPAGE) but it won't risk to increase the
/linux-4.1.27/tools/vm/
Dpage-types.c876 if (madvise(ptr, len, MADV_RANDOM)) in walk_file()
894 if (madvise(ptr, len, MADV_SEQUENTIAL)) in walk_file()
/linux-4.1.27/arch/parisc/kernel/
Dsyscall_table.S198 ENTRY_SAME(madvise)
/linux-4.1.27/arch/powerpc/include/asm/
Dsystbl.h212 SYSCALL_SPU(madvise)
/linux-4.1.27/arch/s390/kernel/
Dcompat_wrapper.c150 COMPAT_SYSCALL_WRAP3(madvise, unsigned long, start, size_t, len, int, behavior);
/linux-4.1.27/arch/x86/syscalls/
Dsyscall_64.tbl37 28 common madvise sys_madvise
Dsyscall_32.tbl228 219 i386 madvise sys_madvise
/linux-4.1.27/tools/perf/bench/
Dnuma.c334 ret = madvise(buf, bytes, MADV_HUGEPAGE); in alloc_data()
341 ret = madvise(buf, bytes, MADV_NOHUGEPAGE); in alloc_data()
/linux-4.1.27/init/
DKconfig1568 bool "Enable madvise/fadvise syscalls" if EXPERT
1571 This option enables the madvise and fadvise syscalls, used by
/linux-4.1.27/Documentation/virtual/kvm/
Dapi.txt933 example is madvise(MADV_DROP).
/linux-4.1.27/Documentation/
Dkernel-parameters.txt3700 Format: [always|madvise|never]