Home
last modified time | relevance | path

Searched full:doing (Results 1 – 25 of 340) sorted by relevance

12345678910>>...14

/Documentation/driver-api/nvdimm/
Dsecurity.rst71 When doing an update, it is expected that the existing key is removed from
74 keyid when doing the update operation. It is also expected that the new key
98 The command format for doing a secure erase is:
106 The command format for doing an overwrite is:
120 The command format for doing a master update is:
131 The command format for doing a master erase is:
/Documentation/arch/x86/
Dtlb.rst23 entire TLB than doing 2^48/PAGE_SIZE individual flushes.
25 be no collateral damage caused by doing the global flush, and
41 You may be doing too many individual invalidations if you see the
61 Essentially, you are balancing the cycles you spend doing invlpg
/Documentation/admin-guide/nfs/
Dnfsd-admin-interfaces.rst14 Before doing that, NFSD can be told which sockets to listen on by
22 If nfsd is started without doing any of these, then it will create one
/Documentation/arch/sh/
Dregister-banks.rst28 registers when doing exception handling).
32 - Used by do_IRQ() and friends for doing irq mapping based off
/Documentation/ABI/testing/
Dprocfs-diskstats22 13 time spent doing I/Os (ms)
23 14 weighted time spent doing I/Os (ms)
Dsysfs-class-fpga-manager34 * write complete = Doing post programming steps
35 * write complete error = Error while doing post programming
Ddebugfs-ec19 what you are doing! Rebooting afterwards also is a good idea.
Dsysfs-devices-state_synced17 were in at the start of the kernel. The device will stop doing
/Documentation/mm/
Dpage_frags.rst19 advantage to doing this is that multiple calls to get_page can be avoided
39 page via a single call. The advantage to doing this is that it allows for
Dbalance.rst20 to be doing balancing. Page reclamation can be kicked off lazily, that
37 doing fine even with the presence of this problem. In 2.3, due to
/Documentation/driver-api/driver-model/
Dporting.rst25 doing so, they will exported via the sysfs filesystem. sysfs can be
26 mounted by doing::
60 as a module) by doing::
107 the struct to discourage programmers from doing mindless casts
168 with the driver model core by doing::
172 It can later be unregistered by doing::
246 When the driver registers with the bus (e.g. doing pci_register_driver()),
260 core by doing::
/Documentation/core-api/
Dkref.rst146 Don't assume you know what you are doing and use the above construct.
147 First of all, you may not know what you are doing. Second, you may
148 know what you are doing (there are some situations where locking is
150 know what they are doing may change the code or copy the code. It's
234 same lock. Note that doing everything in the release routine is still
/Documentation/admin-guide/
Dabi-testing.rst8 current interface will not break by doing this, unless grave
Drtc.rst66 A user process can monitor these interrupts by doing a read(2) or a
91 the process of doing this, the kernel briefly turns off RTC periodic
92 interrupts, so be aware of this if you are doing serious work. If you
/Documentation/devicetree/bindings/interrupt-controller/
Dmarvell,gicp.txt5 interrupts by doing a memory transaction. It is used by the ICU
/Documentation/filesystems/bcachefs/
DCodingStyle.rst63 Good code is code where you can poke around and see what it's doing -
113 what you're doing you'll be amazed at how patient they're happy to be. Users
121 Spend time doing support and helpdesk stuff. Don't just write code - code isn't
160 often go astray - doing something because it seems like it'll be useful often
/Documentation/filesystems/
Ddirectory-locking.rst81 from the same NFS4 server and doing lookups in one of them has reached
90 a root of separate tree, it gets attached to the directory we are doing a
118 another filesystem; it may be ecryptfs doing operation in the underlying
119 filesystem, overlayfs doing something to the layers, network filesystem
201 generality we can assume that T1 is the one doing a cross-directory
Dfiles.rst16 refcounting model in the kernel, the last task doing
119 without first acquiring a reference on it under rcu lookup. Not doing
/Documentation/wmi/devices/
Dwmi-bmof.rst24 The Binary MOF can be obtained by doing a WMI data block query. The result is
/Documentation/devicetree/bindings/sound/
Dmaxim,max98390.yaml21 description: The calculated temperature data was measured while doing the calibration.
/Documentation/bpf/standardization/
Dabi.rst27 The BPF program needs to store the return value into register R0 before doing an
/Documentation/block/
Dswitching-sched.rst27 The list of defined schedulers can be found by simply doing
/Documentation/devicetree/bindings/soc/fsl/cpm_qe/
Dfsl,qe-firmware.yaml19 inside a QE node that needs it. Doing so eliminates the need for a
/Documentation/networking/
Dipsec.rst45 above scenario. The consequence of doing so is small packet(uncompressed)
/Documentation/admin-guide/cgroup-v1/
Ddevices.rst30 /dev/null. Doing::
34 will remove the default 'a *:* rwm' entry. Doing::

12345678910>>...14