| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 16 # that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y',
22 # CORE_BELL_A so naturally it depends on CORE_BELL_A. So if CORE_BELL_A is 'y'
27 # CORE_BELL_A depends on CORE, so CORE influences CORE_BELL_A.
40 # so trivial to resolve, we provide another example below of practical
41 # implications of this recursive issue where the solution is perhaps not so
|
| /Documentation/sound/cards/ |
| D | hdspm.rst | 5 (translated from German, so no good English ;-),
26 allocated. So also the throughput of the PCI system can be
34 all 64 channels are available for the mixer, so channel count
43 so channel count for the driver
52 so channel count for the driver
75 64 Byte accurate. SO it is not really usable for the
84 large never to small. So if you subtract 64 you always have a
100 (especially graphic) ALSA-Mixer GUIs. So Mixer control has be
107 one, I decided to export the hardware structure, so that of
134 a studio should have working synchronisations setup. So use
[all …]
|
| /Documentation/vm/ |
| D | page_migration.rst | 46 a new cpuset then also all its pages are moved with it so that the
71 so that it cannot vanish while the page migration occurs.
90 is increased so that the page cannot be freed while page migration occurs.
98 3. Lock the new page that we want to move to. It is locked so that accesses to
115 8. The new page is prepped with some settings from the old page so that
138 so will enable access for user space processes not already waiting for
160 It's too specific to a driver so other drivers who want to make their pages
174 as PG_isolated so concurrent isolation in several CPUs skip the page
177 Once page is successfully isolated, VM uses page.lru fields so driver
199 to the driver so VM calls driver's putback_page with migration failed page.
[all …]
|
| /Documentation/ |
| D | bus-virt-phys-mapping.txt | 26 so-called "bus address".
42 things any more complex than necessary, so you can assume that all
61 So when the CPU wants any bus master to write to physical memory 0, it
64 So, for example, depending on how the kernel is actually mapped on the
95 pointer from the kernel. So you can have something like this::
129 So why do we care about the physical address at all? We do need the physical
134 management layer doesn't know about devices outside the CPU, so it
151 conceptually in the same memory space as "real memory" at all, so you cannot
153 so on x86 it actually works to just deference a pointer, but it's not
170 * size 1MB, so that we can access it: We can directly
[all …]
|
| D | DMA-ISA-LPC.txt | 9 uses the same DMA system so it will be around for quite some time.
24 Kconfig to be dependent on ISA_DMA_API (not ISA) so that nobody tries
31 memory it can access so extra care must be taken when allocating
44 Unfortunately the memory available for ISA DMA is scarce so unless you
91 not atomic so only one driver may fiddle with the registers at a
150 are lost when the system suspends so if your driver relies on the DMA
|
| D | dontdiff | 49 *.so
50 *.so.dbg
243 vdso32.so.dbg
245 vdso64.so.dbg
|
| /Documentation/trace/ |
| D | tracepoint-analysis.rst | 215 - When receiving an event about a PID, it can record who the parent was so
250 6.85% hackbench /lib/i686/cmov/libc-2.9.so
251 2.62% hackbench /lib/ld-2.9.so
255 0.02% perf /lib/i686/cmov/libc-2.9.so
257 0.01% perf /lib/ld-2.9.so
258 0.00% hackbench /lib/i686/cmov/libpthread-2.9.so
264 within the VDSO. With simple binaries, this will often be the case so let's
266 noticed that X was generating an insane amount of page allocations so let's look
285 47.95% Xorg /opt/gfx-test/lib/libpixman-1.so.0.13.1
286 0.09% Xorg /lib/i686/cmov/libc-2.9.so
[all …]
|
| /Documentation/filesystems/ |
| D | hpfs.txt | 34 danger. I tried to write it so that it won't crash if check=normal on
41 When to mark filesystem dirty so that OS/2 checks it.
55 are case sensitive, so for example when you create a file FOO, you can use
61 OS/2 ignores dots and spaces at the end of file name, so this driver does as
71 variable length. OS/2 stores window and icon positions and file types there. So
97 stored in very crazy way. They tried to do it so that link changes when file is
107 America where people don't care much about codepages and so multiple codepages
125 So this driver simply uses first codepage it finds for uppercasing and
150 the old one so the new name doesn't fit in directory node (dnode). And that
154 You encounter this problem only if you have many directories so that
[all …]
|
| D | path-lookup.txt | 10 child with the next element, and so on.
26 dentry that was looked up, so that may be used as the basis for walking the
31 (usually, the root "/" or current working directory). So contention on these
35 (including dcache look-up) completely "store-free" (so, no locks, atomics, or
84 The hash lists are RCU protected, so list walking is not serialised with
95 read-only protection and no durability of results, so care must be taken when
110 it in the new hash bucket. So what is done is to insert the dentry into the
120 dentry. So a seqlock is used to detect when a rename has occurred, and so the
144 pointers intact, so a concurrent list walker that is currently looking at
167 find either 'A' or 'B'. So if a lookup of 'A' returns NULL, a subsequent lookup
[all …]
|
| D | journalling.rst | 16 journal_t is a typedef for a struct pointer, so when you are finally
41 so it knows what the modifications you are actually making are. To do
45 which indicates the end of a transaction are nestable calls, so you can
60 buffer, and once you are have done so you need to call
77 perform, so that the journalling system isn't re-entered on another
85 for transactions to complete and be committed from other tasks, so
86 essentially we are waiting for :c:func:`jbd2_journal_stop`. So to avoid
91 behaviour to :c:func:`jbd2_journal_start` so you can deadlock here just as
111 so that you can do some of your own management. You ask the journalling
|
| /Documentation/usb/ |
| D | iuu_phoenix.rst | 13 This driver is still in beta stage, so bugs can
16 guru, so don't blame me if your system is unstable
71 so sad to have a nice device like the iuu without seeing all color range available.
72 So I have added this option to permit him to see a lot of color ( each activity change the color
82 is an abstraction, so use any speed or parity setting will
|
| D | authorization.rst | 38 devices (this is so because we need to do an authentication phase
47 Imagine you want to implement a lockdown so only devices of type XYZ
84 # Other stuff so others can use it
92 verification stuff with PKI, so you don't depend on a shared secret,
124 So all interfaces would authorized per default.
127 If a deauthorized interface will be authorized so the driver probing must
|
| /Documentation/admin-guide/ |
| D | rtc.rst | 6 something that tracks wall clock time and is battery backed so that it
20 so it's not very portable to non-x86 systems.
30 IRQ, so they can't all issue alarms; and where standard PC RTCs can
49 are reported by interrupt number 8. (Oh! So *that* is what IRQ 8 is
63 built in locking so that only one process is allowed to have the /dev/rtc
74 there has been any interrupt "pileup" so to speak. Just for reference, a
77 frequencies above 1024Hz. So you really should check the high bytes
92 interrupts, so be aware of this if you are doing serious work. If you
99 Rather than write 50 pages describing the ioctl() and so on, it is
|
| /Documentation/hwmon/ |
| D | w83l785ts.rst | 25 of external resistors, so the user cannot change it. Values seen so
44 there is no old value). It seems to work well enough so that you should
|
| /Documentation/media/kapi/ |
| D | v4l2-event.rst | 11 ``id`` field. If unused, then the ``id`` is 0. So an event is uniquely
26 So every ``(type, ID)`` event tuple will have its own
36 list of the :c:type:`v4l2_fh` struct so :ref:`VIDIOC_DQEVENT` will
41 so that an event can be raised by that object. So the ``node`` field can
45 So to summarize:
55 struct :c:type:`v4l2_subscribed_event` so it knows who subscribed an
79 these callbacks can be called from interrupt context, so they must
166 The first event type in the class is reserved for future use, so the first
|
| /Documentation/process/ |
| D | management-style.rst | 13 simple coding style rules, so this document may or may not have anything
26 .. [#f1] This document does so not so much by answering the question, but by
45 manage had better know the details better than you, so if they come to
54 So the name of the game is to **avoid** decisions, at least the big and
56 makes you look like you know what you're doing, so what a kernel manager
126 answer may end up being that both teams get so frustrated by the
171 - spread the "love" out so evenly that nobody really ends up feeling
176 trust somebody who is so clearly hiding their true character.
200 So when you find somebody smarter than you are, just coast along. Your
208 not necessarily translate to other areas. So you might prod people in
[all …]
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 14 units were driven by the HZ tick, so the smallest timeslice was 1/HZ.
19 rule so that nice +19 level would be _exactly_ 1 jiffy. To better
39 So that if someone wanted to really renice tasks, +19 would give a much
51 So for HZ=1000 we changed nice +19 to 5msecs, because that felt like the
83 nice levels were not 'punchy enough', so lots of people had to resort to
100 tasks, regardless of their absolute nice levels. So on the new
|
| /Documentation/powerpc/ |
| D | syscall64-abi.rst | 21 Both a return value and a return error code are returned. cr0.SO is the return
22 error code, and r3 is the return value or error code. When cr0.SO is clear,
23 the syscall succeeded and r3 is the return value. When cr0.SO is set, the
40 cr0 Volatile (cr0.SO is the return error condition)
60 performed in suspended state, so its side effects will be persistent according
75 returning to the caller. This case is not well defined or supported, so this
|
| /Documentation/media/uapi/v4l/ |
| D | pixfmt-intro.rst | 29 Even so, ultimately, some standard formats are needed, so the V4L2
37 immediately to its right, and so on until the end of the top row of
41 leftmost pixel of the second row from the top, and so on. The last row
|
| /Documentation/devicetree/bindings/regulator/ |
| D | hisilicon,hi655x-regulator.txt | 5 So the node of this regulator must be child node of Hi655x
8 The driver uses the regulator core framework, so please also
|
| /Documentation/arm/sa1100/ |
| D | serial_uart.rst | 14 > serial devices", so you will have a range of minors on those majors (the
15 > tty device layer handles this just fine, so you don't have to worry about
18 > So your assignments are:
|
| /Documentation/ide/ |
| D | ChangeLog.ide-floppy.1996-2002 | 2 * Many thanks to Lode Leroy <Lode.Leroy@www.ibase.be>, who tested so many
36 * idefloppy_get_capability_page(), so move it to
37 * idefloppy_begin_format() so that it's not used
60 * Ver 0.98a Oct 29 01 Expose delay value so we can play.
|
| /Documentation/arm/ |
| D | tcm.rst | 7 Some ARM SoC:s have a so-called TCM (Tightly-Coupled Memory).
12 Harvard-architecture, so there is an ITCM (instruction TCM)
15 The size of DTCM or ITCM is minimum 4KiB so the typical
33 CPU so it is usually wise not to overlap any physical RAM with
45 TCMs in two separate banks, so for example an 8KiB ITCM is divided
56 retention mode, so only on-chip RAM is accessible by
|
| /Documentation/x86/ |
| D | orc-unwinder.rst | 37 performance, because the debuginfo is out of band. So if you disable
74 performance, so the speedup over DWARF may be closer to 40x.)
84 so I suspect we'll really only ever need to keep track of the stack
95 paths, and so it already has all the information it needs to be able to
96 generate ORC data from scratch. So it's an easy step to go from stack
114 annotations are needed than what DWARF would need, so they're much more
117 So the advantages of using objtool to generate ORC data are that it
155 with a range of indices for the .orc_unwind table, so that only a small
|
| /Documentation/networking/ |
| D | 6pack.txt | 17 channel. Special control data is exchanged between the PC and the TNC so
20 set and so on. This control data is processed at a higher priority than
21 normal data, so a data stream can be interrupted at any time to issue an
31 so it is easy to detect errors due to problems on the serial line.
55 of a newly bought TNC does not contain 6pack, so you will have to
67 is supplied with a DIP switch so you can easily change between the
121 the 6pack port is called sp instead of sl or ax. So, sp0 would be the
134 so the 6pack driver doesn't know anything about connects or data that
|