Searched refs:madvise (Results 1 – 19 of 19) sorted by relevance
| /linux-4.4.14/tools/testing/selftests/vm/ |
| D | transhuge-stress.c | 40 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()
|
| D | userfaultfd.c | 387 if (madvise(area_src, nr_pages * page_size, MADV_DONTNEED)) { in stress()
565 if (madvise(area_dst, nr_pages * page_size, MADV_DONTNEED)) { in userfaultfd_stress()
|
| /linux-4.4.14/Documentation/vm/ |
| D | ksm.txt | 24 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.
|
| D | transhuge.txt | 85 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
187 "transparent_hugepage=madvise" or "transparent_hugepage=never"
|
| D | hwpoison.txt | 100 madvise(MADV_HWPOISON, ....)
|
| /linux-4.4.14/arch/um/os-Linux/ |
| D | process.c | 183 err = madvise(addr, length, MADV_REMOVE); in os_drop_memory()
210 if (madvise(addr, UM_KERN_PAGE_SIZE, MADV_REMOVE) != 0) { in can_drop_memory()
|
| /linux-4.4.14/mm/ |
| D | Makefile | 36 obj-$(CONFIG_ADVISE_SYSCALLS) += madvise.o
|
| D | madvise.c | 460 SYSCALL_DEFINE3(madvise, unsigned long, start, size_t, len_in, int, behavior) in SYSCALL_DEFINE3() argument
|
| D | Kconfig | 422 bool "madvise"
424 Enabling Transparent Hugepage madvise, will only provide a
426 madvise(MADV_HUGEPAGE) but it won't risk to increase the
|
| /linux-4.4.14/tools/vm/ |
| D | page-types.c | 878 if (madvise(ptr, len, MADV_RANDOM)) in walk_file()
896 if (madvise(ptr, len, MADV_SEQUENTIAL)) in walk_file()
|
| /linux-4.4.14/arch/parisc/kernel/ |
| D | syscall_table.S | 198 ENTRY_SAME(madvise)
|
| /linux-4.4.14/arch/powerpc/include/asm/ |
| D | systbl.h | 212 SYSCALL_SPU(madvise)
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | compat_wrapper.c | 118 COMPAT_SYSCALL_WRAP3(madvise, unsigned long, start, size_t, len, int, behavior);
|
| /linux-4.4.14/arch/x86/entry/syscalls/ |
| D | syscall_64.tbl | 37 28 common madvise sys_madvise
|
| D | syscall_32.tbl | 228 219 i386 madvise sys_madvise
|
| /linux-4.4.14/tools/perf/bench/ |
| D | numa.c | 339 ret = madvise(buf, bytes, MADV_HUGEPAGE); in alloc_data()
346 ret = madvise(buf, bytes, MADV_NOHUGEPAGE); in alloc_data()
|
| /linux-4.4.14/init/ |
| D | Kconfig | 1579 bool "Enable madvise/fadvise syscalls" if EXPERT
1582 This option enables the madvise and fadvise syscalls, used by
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | api.txt | 964 example is madvise(MADV_DROP).
|
| /linux-4.4.14/Documentation/ |
| D | kernel-parameters.txt | 3820 Format: [always|madvise|never]
|