Home
last modified time | relevance | path

Searched refs:how (Results 1 – 25 of 935) sorted by relevance

12345678910>>...38

/Linux-v5.4/fs/autofs/
Dexpire.c12 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.4/Documentation/ABI/testing/
Dsysfs-kernel-mm-ksm19 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
40 sleep_millisecs: how many milliseconds ksm should sleep between
Dsysfs-kernel-slab19 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 …]
Dsysfs-class-led-trigger-oneshot6 Specifies for how many milliseconds the LED has to stay at
15 Specifies for how many milliseconds the LED has to stay at
/Linux-v5.4/tools/perf/util/
Dordered-events.c266 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.4/security/smack/
DKconfig14 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.4/arch/alpha/kernel/
Dprocess.c78 struct halt_info *how = (struct halt_info *)generic_ptr; in common_shutdown_1() local
106 if (how->mode == LINUX_REBOOT_CMD_RESTART) { in common_shutdown_1()
107 if (!how->restart_cmd) { in common_shutdown_1()
150 alpha_mv.kill_arch(how->mode); in common_shutdown_1()
152 if (! alpha_using_srm && how->mode != LINUX_REBOOT_CMD_RESTART) { in common_shutdown_1()
/Linux-v5.4/Documentation/firmware-guide/acpi/
Dextcon-intel-int3496.rst9 This ACPI device describes how the OS can read the id-pin of the devices'
10 USB-otg port, as well as how it optionally can enable Vbus output on the
11 otg port and how it can optionally control the muxing of the data pins
/Linux-v5.4/Documentation/admin-guide/mm/
Dksm.rst82 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.4/drivers/net/ethernet/intel/
DKconfig47 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
246 devices. For more information on how to identify your adapter, go
279 information on how to identify your adapter, go to the Adapter
299 devices. For more information on how to identify your adapter, go
[all …]
/Linux-v5.4/Documentation/filesystems/
Dindex.rst6 comprehensive information on how the Linux virtual filesystem (VFS) layer
13 See these manuals for documentation about the VFS layer itself and how its
/Linux-v5.4/Documentation/driver-api/dmaengine/
Dindex.rst22 This book is a guide to device driver writers on how to use the Slave-DMA
33 This book introduces how to test DMA drivers using dmatest module.
/Linux-v5.4/drivers/staging/speakup/
Dvarhandlers.c178 int spk_set_num_var(int input, struct st_var_header *var, int how) in spk_set_num_var() argument
190 switch (how) { in spk_set_num_var()
277 int spk_set_mask_bits(const char *input, const int which, const int how) in spk_set_mask_bits() argument
282 if (how & 1) { in spk_set_mask_bits()
304 if (how & 2) { in spk_set_mask_bits()
Dspeakup.h61 int spk_set_num_var(int val, struct st_var_header *var, int how);
63 int spk_set_mask_bits(const char *input, const int which, const int how);
/Linux-v5.4/security/selinux/
DKconfig10 If you are unsure how to answer this question, answer N.
24 If you are unsure how to answer this question, answer N.
45 If you are unsure how to answer this question, answer N.
87 If you are unsure how to answer this question, answer 0.
/Linux-v5.4/arch/sh/kernel/
Dsh_bios.c60 void sh_bios_shutdown(unsigned int how) in sh_bios_shutdown() argument
62 sh_bios_call(BIOS_CALL_SHUTDOWN, how, 0, 0, 0); in sh_bios_shutdown()
/Linux-v5.4/samples/
DKconfig26 different kobject sample modules showing how to use kobjects,
53 different kfifo sample modules showing how to use the
62 Build an example of how to dynamically add the hello
72 Build an QMI client sample driver, which demonstrates how to
79 Build an rpmsg client sample driver, which demonstrates how
/Linux-v5.4/Documentation/
Dindex.rst23 (GPLv2), how to properly mark the license of individual files in the source
66 These manuals contain overall information about how to develop the kernel.
69 knowing how things are done will make the process of getting your changes
88 These books get into the details of how specific kernel subsystems work
/Linux-v5.4/fs/nfs/
Dwrite.c1386 static int flush_task_priority(int how) in flush_task_priority() argument
1388 switch (how & (FLUSH_HIGHPRI|FLUSH_LOWPRI)) { in flush_task_priority()
1400 struct rpc_task_setup *task_setup_data, int how) in nfs_initiate_write() argument
1402 int priority = flush_task_priority(how); in nfs_initiate_write()
1683 int how, int flags) in nfs_initiate_commit() argument
1686 int priority = flush_task_priority(how); in nfs_initiate_commit()
1711 if (how & FLUSH_SYNC) in nfs_initiate_commit()
1797 nfs_commit_list(struct inode *inode, struct list_head *head, int how, in nfs_commit_list() argument
1812 data->mds_ops, how, 0); in nfs_commit_list()
1903 int how, struct nfs_commit_info *cinfo) in nfs_generic_commit_list() argument
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/
Dbrcm,bcm7120-l2-intc.txt11 - controls how some of the interrupts will be flowing, whether they will
61 - brcm,int-map-mask: 32-bits bit mask describing how many and which interrupts
62 are wired to this 2nd level interrupt controller, and how they match their
/Linux-v5.4/Documentation/filesystems/nfs/
Dknfsd-stats.txt47 Counts how many NFS packets have arrived. More precisely, this
57 of how much CPU load is being placed on the sunrpc server layer
61 Counts how many times an NFS transport is enqueued to wait for
77 Counts how many times an idle nfsd thread is woken to try to
86 Counts how many times an nfsd thread triggered an idle timeout,
/Linux-v5.4/security/
DKconfig20 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.4/Documentation/process/
Dhowto.rst7 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 …]
/Linux-v5.4/tools/testing/ktest/examples/
DREADME3 is broken up by task which makes it easier to understand how to set up
26 included into other configs. This is a real use example that shows how
/Linux-v5.4/Documentation/driver-api/gpio/
Dintro.rst9 The documents in this directory give detailed instructions on how to access
10 GPIOs in drivers, and how to write a driver for a device that provides GPIOs
44 firmware knowing how they're used).
49 options about how that value is driven, so that for example only one
122 example, that's how I2C clocks are stretched: a slave that needs a slower clock

12345678910>>...38