Home
last modified time | relevance | path

Searched refs:doing (Results 1 – 25 of 341) sorted by relevance

12345678910>>...14

/Linux-v4.19/kernel/
Dparams.c122 const char *doing, in parse_one() argument
129 const char *doing, void *arg)) in parse_one()
155 pr_debug("doing %s: %s='%s'\n", doing, param, val); in parse_one()
156 return handle_unknown(param, val, doing, arg); in parse_one()
164 char *parse_args(const char *doing, in parse_args() argument
172 const char *doing, void *arg)) in parse_args()
180 pr_debug("doing %s, parsing ARGS: '%s'\n", doing, args); in parse_args()
191 ret = parse_one(param, val, doing, params, num, in parse_args()
195 doing, param); in parse_args()
201 pr_err("%s: Unknown parameter `%s'\n", doing, param); in parse_args()
[all …]
/Linux-v4.19/Documentation/ABI/testing/
Dprocfs-diskstats21 13 - time spent doing I/Os (ms)
22 14 - weighted time spent doing I/Os (ms)
Ddebugfs-ec18 what you are doing! Rebooting afterwards also is a good idea.
/Linux-v4.19/Documentation/x86/
Dtlb.txt15 entire TLB than doing 2^48/PAGE_SIZE individual flushes.
17 be no collateral damage caused by doing the global flush, and
33 You may be doing too many individual invalidations if you see the
53 Essentially, you are balancing the cycles you spend doing invlpg
/Linux-v4.19/Documentation/sh/
Dregister-banks.txt25 registers when doing exception handling).
27 - Used by do_IRQ() and friends for doing irq mapping based off
/Linux-v4.19/Documentation/filesystems/nfs/
Dnfsd-admin-interfaces.txt13 Before doing that, NFSD can be told which sockets to listen on by
21 If nfsd is started without doing any of these, then it will create one
/Linux-v4.19/fs/exofs/
DBUGS3 unmounted and mounted the kernel can get into an endless loop doing a readdir.
/Linux-v4.19/Documentation/driver-model/
Dporting.txt24 doing so, they will exported via the sysfs filesystem. sysfs can be
25 mounted by doing
58 as a module) by doing:
105 the struct to discourage programmers from doing mindless casts
166 with the driver model core by doing:
170 It can later be unregistered by doing:
244 When the driver registers with the bus (e.g. doing pci_register_driver()),
258 core by doing:
/Linux-v4.19/Documentation/vm/
Dpage_frags.rst21 advantage to doing this is that multiple calls to get_page can be avoided
41 page via a single call. The advantage to doing this is that it allows for
/Linux-v4.19/Documentation/
Dkref.txt142 Don't assume you know what you are doing and use the above construct.
143 First of all, you may not know what you are doing. Second, you may
144 know what you are doing (there are some situations where locking is
146 know what they are doing may change the code or copy the code. It's
230 same lock. Note that doing everything in the release routine is still
Dsiphash.txt27 If you're not deriving your key from here, you're doing it wrong.
85 want to pass a pre-filled struct to siphash. When doing this, it's important
140 If you're not deriving your key from here, you're doing it wrong.
/Linux-v4.19/Documentation/ide/
Dwarm-plug-howto.txt16 no other active references to devices before doing "delete_devices" step,
/Linux-v4.19/arch/nios2/
DKconfig158 Say N here unless you know what you are doing.
172 Say N here unless you know what you are doing.
184 Say N here unless you know what you are doing.
/Linux-v4.19/arch/microblaze/
DKconfig156 Unless you know what you are doing, say N here.
193 Say N here unless you know what you are doing.
219 Say N here unless you know what you are doing.
234 Say N here unless you know what you are doing.
/Linux-v4.19/Documentation/devicetree/bindings/interrupt-controller/
Dmarvell,gicp.txt5 interrupts by doing a memory transaction. It is used by the ICU
/Linux-v4.19/arch/sh/cchips/
DKconfig36 Do not change this unless you know what you are doing.
/Linux-v4.19/Documentation/devicetree/bindings/iio/proximity/
Ddevantech-srf04.txt15 Thus this GPIO is set while the ultrasonic waves are doing
/Linux-v4.19/Documentation/block/
Dcfq-iosched.txt229 on rotational media. For example, if a process is doing dependent
239 All cfq queues doing synchronous sequential IO go on to sync-idle tree.
267 For example, if there are 10 sequential readers doing IO and they get
280 scheduled for another second. A process doing small fsync, will suffer
283 Hence doing tree idling on threads using !REQ_IDLE flag on requests
288 A2. I would think whenever one is doing synchronous write and expecting
Dwriteback_cache_control.txt59 data can be completed successfully without doing any work. Drivers for
72 doing:
/Linux-v4.19/drivers/lightnvm/
DKconfig16 only do this if you know what you are doing.
/Linux-v4.19/net/unix/
DKconfig20 Say Y unless you know what you are doing.
/Linux-v4.19/arch/alpha/
DKconfig.debug38 order to debug the code. Say Y unless you know what you are doing.
/Linux-v4.19/Documentation/crypto/
Dcrypto_engine.rst30 - prepare_request: (taking a function pointer) If you need to do some processing before doing the r…
/Linux-v4.19/sound/core/seq/
DKconfig11 unless you know what you're doing.
/Linux-v4.19/drivers/mtd/spi-nor/
DKconfig102 Say N here unless you know what you are doing. Overwriting the
119 Say N here unless you know what you are doing. Overwriting the

12345678910>>...14