Home
last modified time | relevance | path

Searched refs:doing (Results 1 – 200 of 323) sorted by relevance

12

/linux-4.4.14/Documentation/ABI/testing/
Dprocfs-diskstats20 13 - time spent doing I/Os (ms)
21 14 - weighted time spent doing I/Os (ms)
Ddebugfs-ec18 what you are doing! Rebooting afterwards also is a good idea.
Dsysfs-class-fpga-manager36 * write complete error = Error while doing post programming
Dsysfs-class-mtd161 bitflip_threshold. Users are discouraged from doing this,
162 however, unless they know what they are doing and have intimate
Dsysfs-block16 10 - time spent doing I/Os (ms)
17 11 - weighted time spent doing I/Os (ms)
Dsysfs-firmware-dmi-entries25 is doing. Machine to machine experiences will vary.
/linux-4.4.14/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()
216 char *parse_args(const char *doing, in parse_args() argument
224 const char *doing, void *arg)) in parse_args()
232 pr_debug("doing %s, parsing ARGS: '%s'\n", doing, args); in parse_args()
243 ret = parse_one(param, val, doing, params, num, in parse_args()
247 doing, param); in parse_args()
253 pr_err("%s: Unknown parameter `%s'\n", doing, param); in parse_args()
[all …]
/linux-4.4.14/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
Dentry_64.txt55 not* use SWAPGS blindly - nor must we forget doing a SWAPGS when it's
Dmtrr.txt218 fprintf (stderr, "Error doing ioctl(2) on /dev/mtrr\t%s\n", ERRSTRING);
320 fprintf (stderr, "Error doing ioctl(2) on /dev/mtrr\t%s\n", ERRSTRING);
Dearlyprintk.txt120 kernel message by for example doing:
/linux-4.4.14/Documentation/sh/
Dregister-banks.txt25 registers when doing exception handling).
27 - Used by do_IRQ() and friends for doing irq mapping based off
Dnew-machine.txt238 list. The method for doing this is self explanatory, and so we won't waste
/linux-4.4.14/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-4.4.14/fs/exofs/
DBUGS3 unmounted and mounted the kernel can get into an endless loop doing a readdir.
/linux-4.4.14/arch/mn10300/mm/
Dcache-dbg-inv-by-tag.S98 # wait for the cache to finish what it's doing
Dcache-inv-by-tag.S251 # wait for the cache to finish what it's doing
/linux-4.4.14/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:
Doverview.txt58 they're doing when switching between the bus driver and the global driver,
/linux-4.4.14/Documentation/
Dkref.txt116 Don't assume you know what you are doing and use the above construct.
117 First of all, you may not know what you are doing. Second, you may
118 know what you are doing (there are some situations where locking is
120 know what they are doing may change the code or copy the code. It's
204 same lock. Note that doing everything in the release routine is still
Diostats.txt84 Field 10 -- # of milliseconds spent doing I/Os
86 Field 11 -- weighted # of milliseconds spent doing I/Os
89 (field 9) times the number of milliseconds spent doing I/O since the
Dkernel-per-CPU-kthreads.txt77 do not offline any other CPUs, because doing so could force the
133 offline any other CPUs, because doing so could force the timer
137 adaptive-ticks state by doing all of the following:
148 doing all of the following:
Dcpu-load.txt17 system spent 10.01% of the time doing work in user space, 2.92% in the
Drtc.txt66 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
DSubmitChecklist96 source code that explains the logic of what they are doing and why.
Dcrc32.txt105 You can also mix and match the two loop styles, for example doing the
138 producing a 48-bit intermediate remainder. Rather than doing a single
DManagementStyle51 makes you look like you know what you're doing, so what a kernel manager
106 actually do the work also think twice about whether it's worth doing or
202 are doing something irreversible when you _do_ prod them in some
Dramoops.txt58 be set through that platform data. An example of doing that is:
DHOWTO53 of doing things.
188 some task to start doing to join into the kernel development community,
476 - "I've being doing this for 20 years, so..."
509 the exact opposite of what companies are used to doing. Your proposal
511 you can receive feedback on what you are doing. It also lets the
Dfutex-requeue-pi.txt6 left without an owner if it has waiters; doing so would break the PI
Ddell_rbu.txt86 The entries can be recreated by doing the following
Dpreempt-locking.txt121 local_irq_save. Note, when doing so, you must be very careful to not cause
Doops-tracing.txt12 what you were doing. If it occurs repeatably try and describe how to recreate
137 I get worried that I've been doing this for too long ;-)
Dpi-futex.txt56 Most of the technical counter-arguments against doing priority
Dlocal_ops.txt61 different CPU between getting the per-cpu variable and doing the
DSubmittingDrivers98 driver uses as little power as possible when it's not doing
Deisa.txt190 Unfortunately, most drivers are doing the probing by themselves, and
Dvgaarbiter.txt125 resources, the arbiter will first check whether the card is doing legacy
Dbus-virt-phys-mapping.txt25 completely internal to the CPU itself with the CPU doing the appropriate
DBUG-HUNTING20 not confident in doing that please report the bug to your distribution vendor
Dcachetlb.txt317 about doing this.
387 coherency. It must do this by flushing the vmap range before doing
DDMA-API.txt304 aborting the request or even oopsing is better than doing nothing and
477 memory or doing partial flushes.
491 boundaries when doing this.
Dkmemleak.txt110 when doing development. To work around these situations you can use the
Dassoc_array.txt64 RCU readlock is being held by the thread doing the look up.
573 so as long as anyone doing walking or iteration holds the RCU read lock, the
Dkobject.txt178 kobject core, so the caller does not have to worry about doing that by
392 kobject_put(). By doing this, the kobject core will automatically clean up
Dmemory-barriers.txt1189 The CPU being busy doing a ---> --->| A->0 |~~~~ | |
1220 The CPU being busy doing a ---> --->| A->0 |~~~~ | |
1242 The CPU being busy doing a ---> --->| A->0 |~~~~ | |
1363 Prevent both the compiler and the CPU from doing this as follows:
1386 Use READ_ONCE() to prevent the compiler from doing this to you:
1410 Again, use READ_ONCE() to prevent the compiler from doing this:
1878 One key point is that we are only talking about the CPU doing
2556 doing, be it inX()/outX() or readX()/writeX().
2788 Not all systems maintain cache coherency with respect to devices doing DMA. In
Dmodule-signing.txt192 Finally, it is possible to add additional public keys by doing:
Djava.txt5 support of Java Binaries in the OS, Linux is doing it!
Ddma-buf-sharing.txt437 The problem with doing this via a separate fcntl() call, versus doing it
Datomic_ops.txt166 the compiler from doing this, write something like:
173 Don't even -think- about doing this without proper use of memory barriers,
Dstable_api_nonsense.txt182 proven type of development model must be doing something right :)
DCodingStyle368 shouldn't exceed 5-10, or you're doing something wrong. Re-think the
870 do so, though, and doing so unnecessarily can limit optimization.
885 files; doing so makes code harder to read and logic harder to follow. Instead,
/linux-4.4.14/Documentation/ide/
Dwarm-plug-howto.txt16 no other active references to devices before doing "delete_devices" step,
DChangeLog.ide-cd.1994-2004197 * - Fix the I/O error when doing eject without a medium
205 * ide-scsi. TODO: non-modular way of doing the
Dide.txt132 If, after doing all of the above, mount doesn't work and you see
/linux-4.4.14/drivers/staging/media/cxd2099/
DTODO7 doing it, as seen at:
/linux-4.4.14/arch/nios2/
DKconfig163 Say N here unless you know what you are doing.
177 Say N here unless you know what you are doing.
189 Say N here unless you know what you are doing.
/linux-4.4.14/arch/avr32/mach-at32ap/
DKconfig12 when doing little-endian port access.
/linux-4.4.14/arch/microblaze/
DKconfig145 Unless you know what you are doing, say N here.
182 Say N here unless you know what you are doing.
208 Say N here unless you know what you are doing.
223 Say N here unless you know what you are doing.
/linux-4.4.14/arch/sh/cchips/
DKconfig35 Do not change this unless you know what you are doing.
/linux-4.4.14/net/unix/
DKconfig20 Say Y unless you know what you are doing.
/linux-4.4.14/Documentation/block/
Dcfq-iosched.txt230 on rotational media. For example, if a process is doing dependent
240 All cfq queues doing synchronous sequential IO go on to sync-idle tree.
268 For example, if there are 10 sequential readers doing IO and they get
281 scheduled for another second. A process doing small fsync, will suffer
284 Hence doing tree idling on threads using REQ_NOIDLE flag on requests
289 A2. I would think whenever one is doing synchronous write and not expecting
Dwriteback_cache_control.txt59 data can be completed successfully without doing any work. Drivers for
72 doing:
Dswitching-sched.txt29 The list of defined schedulers can be found by simply doing
/linux-4.4.14/drivers/lightnvm/
DKconfig15 only do this if you know what you are doing.
/linux-4.4.14/arch/alpha/
DKconfig.debug40 order to debug the code. Say Y unless you know what you are doing.
/linux-4.4.14/Documentation/xtensa/
Datomctl.txt18 doing a Cached (WB) transaction and use the Memory RCW for un-cached
/linux-4.4.14/tools/testing/selftests/rcutorture/doc/
Drcu-test-image.txt3 probably much better ways of doing this, and this filesystem could no
Dinitrd.txt4 this case. There are probably much better ways of doing this.
/linux-4.4.14/lib/
DKconfig.kasan49 This is a test module doing various nasty things like
DKconfig142 Only choose this option if you know what you are doing.
150 Only choose this option if you know what you are doing.
/linux-4.4.14/block/
DKconfig.iosched21 a new point in the service tree and doing a batch of IO from there
/linux-4.4.14/Documentation/arm/SA1100/
Dserial_UART12 > doing anything special.)
DItsy12 serial console (to see what you're doing). No other devices have been
/linux-4.4.14/net/caif/
DKconfig30 Be aware that doing this will impact performance.
/linux-4.4.14/Documentation/fb/
Dcmap_xfbdev.txt50 that the app wants to match to. The above code is doing what looks like a least
Dsstfb.txt60 the device will be /dev/fb0. You can check this by doing a
Dfbcon.txt211 4. If fbcon is compiled as a module, load fbcon by doing:
/linux-4.4.14/drivers/net/wireless/ath/ath5k/
DKconfig74 unless doing research.
/linux-4.4.14/Documentation/networking/
Dltpc.txt101 Instead, you follow the same procedure as for doing IP in EtherTalk.
127 work, and to Denis Hainsworth for doing the bleeding-edge testing.
Dipsec.txt37 above scenario. The consequence of doing so is small packet(uncompressed)
Dmac80211-injection.txt56 (which is easier than doing the work to bind the socket to the right
Ddns_resolver.txt69 implemented in the module can be called after doing:
Dfib_trie.txt77 towards the root from a given tnode, doing a resize() at each step
D3c509.txt43 for LILO parameters for doing this:
Ddecnet.txt207 then your computer will be doing more work than required. Some cards
Dnetdev-FAQ.txt215 doing so. If your change is a bug-fix, make sure your commit log
/linux-4.4.14/Documentation/frv/
Dgdbstub.txt62 interrupt it or wait for an exception to occur before doing anything with
72 computer doing the debugging:
Dbooting.txt80 doing anything else. See the section on kernel debugging with GDB.
Dkernel-ABI.txt199 determines that nothing needs doing. This is done simply with an
Dfeatures.txt99 The reasons for doing this are: (1) the page at address 0 should be
/linux-4.4.14/net/xfrm/
DKconfig68 Say Y unless you know what you are doing.
/linux-4.4.14/Documentation/sound/oss/
DSoundPro29 The chip is capable of doing full-duplex, but since the driver sees it as an
44 of doing this. The most common is to use the isapnptools package to
/linux-4.4.14/net/ax25/
DKconfig55 DAMA is a mechanism to prevent collisions when doing AX.25
70 DAMA is a mechanism to prevent collisions when doing AX.25
/linux-4.4.14/arch/powerpc/
DKconfig582 Say N unless you know what you are doing.
877 Unless you know what you are doing, say N here.
892 Say N here unless you know what you are doing.
908 Say N here unless you know what you are doing.
964 Say N here unless you know what you are doing.
979 Say N here unless you know what you are doing.
993 Say N here unless you know what you are doing.
1016 Say N here unless you know what you are doing.
/linux-4.4.14/Documentation/vm/
Dbalance16 to be doing balancing. Page reclamation can be kicked off lazily, that
33 doing fine even with the presence of this problem. In 2.3, due to
/linux-4.4.14/drivers/s390/char/
DKconfig91 You should only select this option if you know what you are doing,
101 You should only select this option if you know what you are doing,
/linux-4.4.14/Documentation/filesystems/
Decryptfs.txt71 levels unless you are doing so for the sole purpose of debugging or
Disofs.txt12 There is also an option of doing UTF-8 translations with the
Dsysfs.txt27 it by doing:
63 Mixing types, expressing multiple lines of data, and doing fancy
108 is equivalent to doing:
Dfiles.txt13 refcounting model in the kernel, the last task doing
Dvfat.txt52 There is also an option of doing UTF-8 translations
146 without doing anything or remount the partition in
Dxfs-delayed-logging-design.txt71 doing aggregation of transactions in memory - batching them, if you like - to
100 wasting space. When we are doing repeated operations on the same set of
106 From a conceptual point of view, XFS is already doing relogging in memory (where
107 memory == log buffer), only it is doing it extremely inefficiently. It is using
534 The simpler way of doing this is tracking the entire log space used by the
643 significant concern. Preventing lots of CPUs spinning doing nothing is the
Dafs.txt126 mounted on /afs in one go by doing:
Dporting318 free the on-disk inode, you may end up doing that while ->write_inode() is writing
400 function type. If you were doing it manually, just switch from setting ->mnt_root
Dxfs-self-describing-metadata.txt45 Hence most of the time spent on forensic analysis is spent doing basic
120 written to the filesystem. One of the key information points when doing forensic
Dlogfs.txt39 required to completely free a segment before doing so.
/linux-4.4.14/arch/arm/boot/compressed/
Dhead-sharpsl.S19 #error What am I doing here...
/linux-4.4.14/Documentation/isdn/
DREADME.syncppp12 to answer the appropriate question when doing a "make config"
/linux-4.4.14/drivers/staging/iio/
DTODO54 There are probably better ways of doing this. The
/linux-4.4.14/Documentation/arm/
Dmem_alignment5 doing so on some f***ed up ARM architectures like the EBSA110. However
DREADME36 (arch/arm/boot/Image). A compressed image can be built by doing a
53 the problem, what you were doing, etc.
Dcluster-pm-race-avoidance.txt98 therefore, a CPU can only be doing one thing at a single point in time.
201 Because a cluster contains multiple CPUs, it can be doing multiple
/linux-4.4.14/net/atm/
DKconfig73 you know what you are doing.
/linux-4.4.14/Documentation/prctl/
Dno_new_privs.txt5 careful to prevent the parent from doing anything that could subvert the
/linux-4.4.14/Documentation/power/
Dsuspend-and-interrupts.txt15 The rationale for doing so is that after the "late" phase of device suspend
29 callbacks for devices). The function doing that is resume_device_irqs().
Dfreezing-of-tasks.txt117 additional memory and we prevent them from doing that by freezing them earlier.
176 2. Now that we have FUSE, plus the framework for doing device drivers in
178 now doing the sorts of things that kernel threads do
/linux-4.4.14/Documentation/device-mapper/
Dstatistics.txt162 10. the number of milliseconds spent doing I/Os
163 11. the weighted number of milliseconds spent doing I/Os
Dpersistent-data.txt45 transaction manager is by shadowing an existing block (ie. doing
Dlog-writes.txt85 then replay from that point on doing the fsck check in the
/linux-4.4.14/net/ipx/
DKconfig59 If you don't know what you are doing, say N.
/linux-4.4.14/Documentation/scsi/
Din2000.txt61 with it, start by doing 'cat /proc/scsi/in2000/0'. You
115 One nifty new feature is a cool way of doing disconnect/
Dqlogicfas.txt63 that the file copied properly. (Turn off all caching when doing these
DNinjaSCSI.txt108 If you eject card when doing some operation for your SCSI device or suspend
Dtmscsim.txt410 having your box spending most of its time doing the logging.
426 doing this during early revisions).
/linux-4.4.14/fs/ntfs/
DKconfig40 you can enable debugging messages by doing (as root):
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.freeze55 doing DMA at the same time. bttv + ide seems to cause this sometimes,
/linux-4.4.14/arch/powerpc/boot/dts/
Dmvme5100.dts108 * 0x2 to anything else, doing so will cause endless
/linux-4.4.14/arch/nios2/platform/
DKconfig.platform106 Say N here unless you know what you are doing.
/linux-4.4.14/drivers/staging/iio/Documentation/
Dsysfs-bus-iio-light46 value and doing the negation in sw.
/linux-4.4.14/fs/reiserfs/
DREADME144 Yuri Shevchuk and Nikita Danilov are doing squid cache optimization.
146 Vitaly Fertman is doing fsck.
/linux-4.4.14/drivers/usb/core/
DKconfig32 if you know exactly what you are doing.
/linux-4.4.14/Documentation/ABI/
DREADME24 current interface will not break by doing this, unless grave
/linux-4.4.14/tools/power/cpupower/bench/
DREADME-BENCH7 - Identify worst case performance loss when doing dynamic frequency
/linux-4.4.14/Documentation/dmaengine/
Dprovider.txt15 entities that will be doing the copy, and requests what endpoints are
31 physical bus allows to maximize performances when doing a simple
59 over that collection, doing whatever we programmed there.
/linux-4.4.14/Documentation/input/
Damijoy.txt154 This should be noted when doing variable beam displays.
Dyealink.txt212 - Olivier Vandorpe, for starting the usbb2k-api project doing much of
Djoystick.txt207 is not recommended unless you really know what are you doing. It's not
459 doing this, the device will be reported and will start working.
/linux-4.4.14/include/linux/
Dmoduleparam.h328 const char *doing, void *arg));
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt55 workloads and can fully utilize the bandwidth to the servers when doing bulk
/linux-4.4.14/Documentation/thermal/
Dintel_powerclamp.txt143 calibration is implemented. The goals for doing such a calibration
231 effectiveness. The extreme case would be doing a ping -f to generated
/linux-4.4.14/Documentation/scheduler/
Dsched-domains.txt37 While doing that, it checks to see if the current domain has exhausted its
Dsched-rt-group.txt22 root only and assumes root knows what he is doing.
/linux-4.4.14/Documentation/ia64/
Defirtc.txt38 One of the reasons for doing it this way is to allow for EFI to still evolve
/linux-4.4.14/arch/m68k/
DKconfig.cpu337 you are doing.
357 really know what you are doing, say N. Try Y only if you're quite
/linux-4.4.14/arch/powerpc/platforms/ps3/
DKconfig26 what you are doing.
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dentry.S224 ;; We get here after doing a syscall if extra work might need to be done
505 ;; since *not* doing that saves us from re-entrancy checks. We don't want
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt58 rejecting the new flags/modes or ioctls (since doing that was botched in the
203 lengthy discussions for a more generic solution. And occasionally doing a
Dhdio.txt446 2 = 48-bit doing 28-bit
1035 2 = 48-bit doing 28-bit
/linux-4.4.14/Documentation/usb/
DWUSB-Design-overview.txt322 start enumerating and doing transfers through usb_hcd->urb_enqueue() to
350 when doing a data transfer (xfer), first the rpipe has to be aimed and
360 [This sucks, because doing USB scatter gatter in Linux is resource
Ddma.txt36 - If you're doing lots of small data transfers from the same buffer all
Dhotplug.txt140 choosing drivers to probe(). The thread doing new device processing checks
DCREDITS136 - Ric Klaren <ia_ric@cs.utwente.nl> for doing nice
Dpersist.txt101 devices for which it is enabled. You can enable the feature by doing
Dehci.txt118 usb-storage doing disk I/O; watch the request queues!)
/linux-4.4.14/Documentation/devicetree/
Dusage-model.txt33 however, of creating a new binding without first doing some homework
132 cautioned about doing so at the board level since there is typically a
159 troublesome board(s) in generic setup code, but doing so very quickly
/linux-4.4.14/drivers/block/
DKconfig14 only do this if you know what you are doing.
374 are doing. If you boot from a filesystem that needs to be extracted
383 what you are doing.
/linux-4.4.14/Documentation/laptops/
Dsony-laptop.txt87 you are not afraid of any side effects doing strange things with
/linux-4.4.14/Documentation/security/
Dcredentials.txt244 to the server, regardless of who is actually doing a read or a write upon it.
412 time, and possibly to sleep whilst doing so, then the caller should get a
449 will retrieve 'struct cred::suid' from the task, doing the appropriate RCU
/linux-4.4.14/Documentation/filesystems/caching/
Doperations.txt176 When it has finished doing its processing, it should call
Dobject.txt135 particular work item. These state actions may be doing sequences of
/linux-4.4.14/arch/cris/arch-v32/mach-fs/
DKconfig82 you are doing (may be != 0 for unusual address line
/linux-4.4.14/Documentation/i2c/busses/
Di2c-i801114 well known for first doing this on their P4B motherboard, and many other
/linux-4.4.14/arch/cris/arch-v32/
DKconfig97 you are doing (may be != 0 for unusual address line
/linux-4.4.14/Documentation/sound/alsa/
DProcfile.txt178 Some ELD fields may be modified by doing `echo name hex_value > eld#*`.
/linux-4.4.14/arch/arm/boot/dts/
Darmada-xp-synology-ds414.dts135 * what you are doing.
Darmada-370-synology-ds213j.dts112 * what you are doing.
Dstih416.dtsi501 * you're doing.
/linux-4.4.14/sound/core/
DKconfig42 unless you know what you're doing.
/linux-4.4.14/fs/jffs2/
DREADME.Locking67 No ordering rules have been made for doing so.
/linux-4.4.14/Documentation/trace/
Dmmiotrace.txt88 If you are doing a trace for a driver project, e.g. Nouveau, you should also
/linux-4.4.14/fs/cifs/
DKconfig56 Unless you are a developer or are doing network performance analysis
/linux-4.4.14/arch/cris/arch-v32/drivers/
DKconfig131 you know exactly what you are doing. The only valid reason
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-api.txt43 still responding before doing the write call to ping the watchdog.
/linux-4.4.14/arch/cris/arch-v10/
DREADME.mm93 The MMU can map all 4 GB in user mode, but doing that would mean that a
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DOverview.txt275 The best way of doing this is to make a function that
/linux-4.4.14/fs/affs/
DChanges197 - Fixed bug in add_entry(): When doing a sorted insert,
/linux-4.4.14/arch/cris/arch-v32/kernel/
Dentry.S271 ;; We get here after doing a syscall if extra work might need to be done
/linux-4.4.14/Documentation/blockdev/
Dfloppy.txt133 when doing this tuning. Indeed, it allows to try different
/linux-4.4.14/Documentation/RCU/
Dchecklist.txt120 they are becoming increasingly aggressive about doing
302 primitives when the update-side lock is held is that doing so
DlistRCU.txt189 concurrent reads while doing a copy to perform an update, is what gives
DwhatisRCU.txt111 that readers are not doing any sort of synchronization operations???
279 it was acquired is just as illegal as doing so with normal
528 If the callback for call_rcu() is not doing anything more than calling
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt41 it by doing
142 structure that actually represents what the subsystem is doing. The
/linux-4.4.14/kernel/trace/
DKconfig256 Allow doing a snapshot of a single CPU buffer instead of a
539 Say N, unless you absolutely know what you are doing.
/linux-4.4.14/Documentation/dvb/
DREADME.dvb-usb9 After reading some specs and doing some USB snooping, it realized, that the
/linux-4.4.14/Documentation/timers/
Dtimekeeping.txt55 Since this operation may be invoked very often, doing this in a strict
/linux-4.4.14/drivers/usb/misc/
DKconfig224 driver beforehand. Tools for doing so are available at
/linux-4.4.14/Documentation/virtual/kvm/
Dmsr.txt99 derive per-CPU time by doing:
/linux-4.4.14/arch/mn10300/
DKconfig120 capable of doing LL/SC equivalent operations.
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt1243 It prevents a nasty UML user from doing things like setting the UML IP
1307 other ways of doing the same thing
1505 you're doing, this is the way to go.
2420 up doing is up to /etc/inittab. Normally, it reboots the machine.
2480 ``Compiling the kernel and modules'' for information on doing that.
2668 After you run UML and it sits there doing nothing, you hit return at
3776 Aha! The light dawns. That first page is doing double duty as a
3784 manager. After doing this, and fixing a couple of subsequent buglets,
4358 is doing a real nice job of it. He also noticed and fixed a number of
4364 driver and is doing a nice job of it.
/linux-4.4.14/arch/x86/crypto/
Dpoly1305-sse2-x86_64.S57 # This single block variant tries to improve performance by doing two
/linux-4.4.14/arch/m68k/fpsp040/
Dgen_except.S325 | by doing an fmove <ea>,fp0. The exception operand, in
/linux-4.4.14/scripts/
DKbuild.include33 # Easy method for doing a status message
/linux-4.4.14/Documentation/development-process/
D7.AdvancedTopics118 need to know that you know what you're doing, and I need to be able
/linux-4.4.14/net/ipv4/
DKconfig126 special protocol designed for doing this job), say Y here. In case
143 special protocol designed for doing this job), say Y here. In case
/linux-4.4.14/arch/tile/
DKconfig316 If you are not absolutely sure what you are doing, leave this
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt161 Consider a case where we have two threads, one doing reads and the other,
/linux-4.4.14/Documentation/arm64/
Darm-acpi.txt48 Such bindings could be defined in DT at some point, but doing so means ARM
80 server vendors need. Linux could potentially get there with DT, but doing so
/linux-4.4.14/Documentation/PCI/
Dpci.txt559 on the bus need to be capable of doing it, so this is something which needs
610 expected to wait before doing other work. The classic "bit banging"
/linux-4.4.14/Documentation/cgroups/
Dcpusets.txt392 than one big one, but doing so means that overloads in one of the
429 When doing this, you don't usually want to leave any unpinned tasks in
672 3) Create the new cpuset by doing mkdir's and write's (or echo's) in

12