| /Linux-v5.15/tools/testing/selftests/openat2/ |
| D | openat2_test.c | 158 struct open_how how; member
169 .how.flags = O_TMPFILE | O_PATH | O_RDWR, .err = -EINVAL }, in test_openat2_flags()
171 .how.flags = O_TMPFILE | O_CREAT | O_RDWR, .err = -EINVAL }, in test_openat2_flags()
175 .how.flags = O_PATH | O_CLOEXEC }, in test_openat2_flags()
177 .how.flags = O_PATH | O_DIRECTORY }, in test_openat2_flags()
179 .how.flags = O_PATH | O_NOFOLLOW }, in test_openat2_flags()
182 .how.flags = O_PATH | O_RDWR, .err = -EINVAL }, in test_openat2_flags()
184 .how.flags = O_PATH | O_CREAT, .err = -EINVAL }, in test_openat2_flags()
186 .how.flags = O_PATH | O_EXCL, .err = -EINVAL }, in test_openat2_flags()
188 .how.flags = O_PATH | O_NOCTTY, .err = -EINVAL }, in test_openat2_flags()
[all …]
|
| D | resolve_test.c | 113 struct open_how how; member
139 .path = "/", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
142 .path = "cheeky/absself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
145 .path = "abscheeky/absself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
148 .path = "..", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
151 .path = "../root/", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
154 .path = "cheeky/self", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
157 .path = "abscheeky/self", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
160 .path = "cheeky/garbageself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
163 .path = "abscheeky/garbageself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
[all …]
|
| D | helpers.c | 17 bool needs_openat2(const struct open_how *how) in needs_openat2() argument
19 return how->resolve != 0; in needs_openat2()
22 int raw_openat2(int dfd, const char *path, void *how, size_t size) in raw_openat2() argument
24 int ret = syscall(__NR_openat2, dfd, path, how, size); in raw_openat2()
28 int sys_openat2(int dfd, const char *path, struct open_how *how) in sys_openat2() argument
30 return raw_openat2(dfd, path, how, sizeof(*how)); in sys_openat2()
33 int sys_openat(int dfd, const char *path, struct open_how *how) in sys_openat() argument
35 int ret = openat(dfd, path, how->flags, how->mode); in sys_openat()
98 struct open_how how = {}; in init() local
104 fd = sys_openat2(AT_FDCWD, ".", &how); in init()
|
| D | helpers.h | 27 * Arguments for how openat2(2) should open the target path. If @resolve is
47 bool needs_openat2(const struct open_how *how);
50 /* how->resolve flags for openat2(2). */
94 int raw_openat2(int dfd, const char *path, void *how, size_t size);
95 int sys_openat2(int dfd, const char *path, struct open_how *how);
96 int sys_openat(int dfd, const char *path, struct open_how *how);
|
| /Linux-v5.15/fs/autofs/ |
| D | expire.c | 12 unsigned long timeout, unsigned int how) in autofs_can_expire() argument
20 if (!(how & AUTOFS_EXP_IMMEDIATE)) { in autofs_can_expire()
30 struct dentry *dentry, unsigned int how) in autofs_mount_busy() argument
52 if (how & AUTOFS_EXP_FORCED) { in autofs_mount_busy()
153 unsigned int how) in autofs_direct_busy() argument
158 if (how & AUTOFS_EXP_FORCED) in autofs_direct_busy()
172 if (!autofs_can_expire(top, timeout, how)) in autofs_direct_busy()
185 unsigned int how) in autofs_tree_busy() argument
207 if (autofs_mount_busy(mnt, p, how)) { in autofs_tree_busy()
231 if (how & AUTOFS_EXP_FORCED) in autofs_tree_busy()
[all …]
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-ksm | 19 full_scans: how many times all mergeable areas have been
22 pages_shared: how many shared pages are being used.
24 pages_sharing: how many more sites are sharing them i.e. how
27 pages_to_scan: how many present pages to scan before ksmd goes
30 pages_unshared: how many pages unique but repeatedly checked
33 pages_volatile: how many pages changing too fast to be placed
41 sleep_millisecs: how many milliseconds ksm should sleep between
|
| D | sysfs-kernel-slab | 19 The aliases file is read-only and specifies how many caches
48 The alloc_fastpath file shows how many objects have been
59 The alloc_from_partial file shows how many times a cpu slab has
71 The alloc_refill file shows how many times the per-cpu freelist
82 The alloc_slab file is shows how many times a new slab had to
93 The alloc_slowpath file shows how many objects have been
115 The cpu_slabs file is read-only and displays how many cpu slabs
124 The file cpuslab_flush shows how many times a cache's cpu slabs
147 The deactivate_empty file shows how many times an empty cpu slab
157 The deactivate_full file shows how many times a full cpu slab
[all …]
|
| /Linux-v5.15/arch/nds32/lib/ |
| D | memmove.S | 21 srli $p1, $r2, #2 ! $p1 is how many words to copy
29 andi $r2, $r2, #3 ! How many bytes are less than a word
35 addi $p1, $p1, #-1 ! How many words left to copy
44 andi $r2, $r2, #3 ! How many bytes are less than a word
50 addi $p1, $p1, #-1 ! How many words left to copy
60 addi $r2, $r2, #-1 ! How many bytes left to copy
|
| D | memset.S | 10 srli $p1, $r2, 2 ! $p1 is how many words to copy
11 andi $r2, $r2, 3 ! How many bytes are less than a word
21 addi $p1, $p1, #-1 ! How many words left to copy
|
| /Linux-v5.15/Documentation/admin-guide/mm/ |
| D | ksm.rst | 82 how many pages to scan before ksmd goes to sleep
88 how many milliseconds ksmd should sleep before next scan
101 sharing of setting 1 (default). You may wish to compare how
153 specifies how frequently KSM checks the metadata of the pages
163 how many shared pages are being used
165 how many more sites are sharing them i.e. how much saved
167 how many pages unique but repeatedly checked for merging
169 how many pages changing too fast to be placed in a tree
171 how many times all mergeable areas have been scanned
|
| /Linux-v5.15/drivers/net/ethernet/intel/ |
| D | Kconfig | 47 adapters. For more information on how to identify your adapter, go
66 use the regular e1000 driver For more information on how to
95 adapters. For more information on how to identify your adapter, go
131 information on how to identify your adapter, go to the Adapter &
148 instead. For more information on how to identify your adapter, go
167 adapters. For more information on how to identify your adapter, go
219 Intel(R) ixgbe driver. For more information on how to identify your
247 devices. For more information on how to identify your adapter, go
280 information on how to identify your adapter, go to the Adapter
305 devices. For more information on how to identify your adapter, go
[all …]
|
| /Linux-v5.15/fs/ |
| D | open.c | 994 struct open_how how = { in build_open_how() local
1000 if (how.flags & O_PATH) in build_open_how()
1001 how.flags &= O_PATH_FLAGS; in build_open_how()
1003 if (!WILL_CREATE(how.flags)) in build_open_how()
1004 how.mode = 0; in build_open_how()
1005 return how; in build_open_how()
1008 inline int build_open_flags(const struct open_how *how, struct open_flags *op) in build_open_flags() argument
1010 u64 flags = how->flags; in build_open_flags()
1032 if (how->resolve & ~VALID_RESOLVE_FLAGS) in build_open_flags()
1036 if ((how->resolve & RESOLVE_BENEATH) && (how->resolve & RESOLVE_IN_ROOT)) in build_open_flags()
[all …]
|
| /Linux-v5.15/security/smack/ |
| D | Kconfig | 14 If you are unsure how to answer this question, answer N.
32 If you are unsure how to answer this question, answer N.
43 If you are unsure how to answer this question, answer N.
55 If you are unsure how to answer this question, answer N.
|
| /Linux-v5.15/Documentation/process/ |
| D | howto.rst | 7 instructions on how to become a Linux kernel developer and how to learn
20 So, you want to learn how to become a Linux kernel developer? Or you
24 and hints on how to work with the community. It will also try to
49 Please remember that you are trying to learn how to work with the
64 rules and how to use `SPDX <https://spdx.org/>`_ identifiers in source code are
79 invaluable for learning how to interact with the kernel community. When
81 documentation files are also added which explain how to use the feature.
109 These files describe in explicit detail how to successfully create
120 Other excellent descriptions of how to create patches properly are:
147 This document describes how Linux kernel maintainers operate and the
[all …]
|
| D | 7.AdvancedTopics.rst | 6 At this point, hopefully, you have a handle on how the development process
27 teach the reader how to use git; that would be sufficient material for a
28 long document in its own right. Instead, the focus here will be on how git
39 understanding of how git works before trying to use it to make patches
111 useful in such situations; it remembers how merge conflicts were resolved
156 learn how to program in the kernel environment than by looking at code
166 comments as questions rather than criticisms. Asking "how does the lock
|
| /Linux-v5.15/security/ |
| D | Kconfig | 20 If you are unsure how to answer this question, answer N.
33 If you are unsure how to answer this question, answer N.
46 If you are unsure how to answer this question, answer N.
55 If you are unsure how to answer this question, answer N.
75 If you are unsure how to answer this question, answer N.
88 If you are unsure how to answer this question, answer N.
97 If you are unsure how to answer this question, answer N.
124 See Documentation/x86/intel_txt.rst for a description of how to enable
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | floating-point.json | 6 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
13 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
20 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
27 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
34 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
41 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
48 …) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
55 …) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
62 …) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
69 …) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
|
| /Linux-v5.15/Documentation/networking/ |
| D | decnet.rst | 41 start working. If you need something more complicated or are unsure how
139 5. How can I tell if its working?
172 6. How to send a bug report
181 - How far though the above set of tests can you get ?
185 - How much data was being transferred ?
187 - How can the problem be reproduced ?
189 tcpdump don't understand how to dump DECnet properly, so including
197 A quick FAQ on ethernet MAC addresses to explain how Linux and DECnet
198 interact and how to get the best performance from your hardware.
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-enum-mbus-code.rst | 101 See :ref:`v4l2-mbus-format` on how to do this.
108 See :ref:`v4l2-mbus-format` on how to do this.
115 See :ref:`v4l2-mbus-format` on how to do this.
122 See :ref:`v4l2-mbus-format` on how to do this.
129 See :ref:`v4l2-mbus-format` on how to do this.
|
| /Linux-v5.15/samples/ |
| D | Kconfig | 45 different kobject sample modules showing how to use kobjects,
72 different kfifo sample modules showing how to use the
81 Build an example of how to dynamically add the hello
91 Build an QMI client sample driver, which demonstrates how to
98 Build an rpmsg client sample driver, which demonstrates how
|
| /Linux-v5.15/Documentation/filesystems/nfs/ |
| D | knfsd-stats.rst | 49 Counts how many NFS packets have arrived. More precisely, this
59 of how much CPU load is being placed on the sunrpc server layer
63 Counts how many times an NFS transport is enqueued to wait for
79 Counts how many times an idle nfsd thread is woken to try to
88 Counts how many times an nfsd thread triggered an idle timeout,
|
| /Linux-v5.15/tools/perf/util/ |
| D | ordered-events.c | 266 static int __ordered_events__flush(struct ordered_events *oe, enum oe_flush how, in __ordered_events__flush() argument
283 switch (how) { in __ordered_events__flush()
320 str[how], oe->nr_events); in __ordered_events__flush()
326 if (how == OE_FLUSH__ROUND) in __ordered_events__flush()
329 oe->last_flush_type = how; in __ordered_events__flush()
333 str[how], oe->nr_events); in __ordered_events__flush()
339 int ordered_events__flush(struct ordered_events *oe, enum oe_flush how) in ordered_events__flush() argument
341 return __ordered_events__flush(oe, how, 0); in ordered_events__flush()
|
| /Linux-v5.15/include/uapi/linux/netfilter/ |
| D | xt_hashlimit.h | 38 __u32 size; /* how many buckets */
62 __u32 size; /* how many buckets */
76 __u32 size; /* how many buckets */
90 __u32 size; /* how many buckets */
|
| /Linux-v5.15/security/selinux/ |
| D | Kconfig | 10 If you are unsure how to answer this question, answer N.
24 If you are unsure how to answer this question, answer N.
48 If you are unsure how to answer this question, answer N.
94 If you are unsure how to answer this question, answer 0.
|
| /Linux-v5.15/Documentation/x86/x86_64/ |
| D | machinecheck.rst | 15 mcelog knows how to decode them.
40 How often to poll for corrected machine check errors, in seconds
56 how hard the kernel tries to recover even at some risk of
75 How long to wait for the other CPUs to machine check too on a
|
