/linux/Documentation/kernel-hacking/ |
H A D | false-sharing.rst | 64 Back in time when one platform had only one or a few CPUs, hot data
|
/linux/Documentation/admin-guide/mm/ |
H A D | zswap.rst | 27 device when the compressed pool reaches its size limit. This requirement had
|
/linux/Documentation/process/ |
H A D | management-style.rst | 45 manage had better know the details better than you, so if they come to 82 work you had people work on for the last year. Suddenly the decision
|
H A D | howto.rst | 508 opinion have had positive experiences. 604 don't give up, it's possible. Many have done it before, and each had to 614 to be based on text he had written, and to Randy Dunlap and Gerrit
|
/linux/Documentation/bpf/ |
H A D | bpf_design_QA.rst | 106 bpf_lookup_map_elem(key) had a requirement that 'key' must be 159 These two already had equivalent instructions in native CPUs.
|
/linux/Documentation/locking/ |
H A D | rt-mutex-design.rst | 71 inherited priority, and A then can continue with the resource that C had. 406 Before this function is called, the task has already had rt_mutex_adjust_prio 485 If the owner is also blocked on a lock, and had its pi_waiters changed
|
/linux/Documentation/driver-api/mtd/ |
H A D | nand_ecc.rst | 596 to 0.075 sec. Actually I had to decide to start measuring over 10 736 introduced by this is about a factor 2 on my system when a repair had to 737 be done, and 1% or so if no repair had to be done.
|
/linux/Documentation/RCU/Design/Requirements/ |
H A D | Requirements.rst | 68 Slingwine and I had this guarantee firmly in mind when we started work 465 explicit memory barrier for publication, but had nothing resembling 614 | schedule() had better prevent calling-code accesses to shared | 734 not be possible if rcu_read_lock() and rcu_read_unlock() had 1346 Interestingly enough, DYNIX/ptx had the equivalents of call_rcu() 1466 10,000 callbacks, or has 10,000 more callbacks than it had the last time 1718 Torvalds recently had to 2150 is non-idle, the scheduling-clock tick had better be running. 2424 Before preemptible RCU, waiting for an RCU grace period had the side 2600 had completely left the trampoline. Worse yet, in some situations [all …]
|
/linux/tools/memory-model/Documentation/ |
H A D | explanation.txt | 170 will again both be 0. (If P1 had been designed to read buf 554 though it had been written there by an imaginary initial store that 716 (As a minor curiosity, if this code had used normal loads instead of 1141 violation of the read-write coherence rule. Similarly, if we had 1201 This could not have happened if the local cache had processed the 1326 in program order. If the second load had executed before the first 1892 index value. By contrast, if the calls had been 1931 is much as if we had written: 2091 in the example had been written as: 2153 P1 had all executed on a single CPU, as in the example before this [all …]
|
/linux/Documentation/driver-api/acpi/ |
H A D | linuxized-acpica.rst | 203 established, there already had been divergences between Linux and
|
/linux/Documentation/networking/ |
H A D | strparser.rst | 146 -ESTRPIPE and the stream parser had previously read some bytes for
|
/linux/Documentation/devicetree/bindings/power/ |
H A D | rockchip-io-domain.yaml | 31 If there were some other software that had the smarts of making
|
/linux/Documentation/core-api/ |
H A D | asm-annotations.rst | 159 ``END``. Except ``END`` had several other meanings too.
|
/linux/Documentation/trace/ |
H A D | timerlat-tracer.rst | 173 dummy_load_1ms_pd_init, which had the following code (on purpose)::
|
/linux/Documentation/sound/cards/ |
H A D | emu-mixer.rst | 23 Intel DP55 board (memory controller in the CPU), but had success with an
|
/linux/arch/x86/math-emu/ |
H A D | README | 200 there was no reason not to use it after I had edited it to be 293 have a value of pi which had about 150 bits precision. The FPU
|
/linux/Documentation/scsi/ |
H A D | ChangeLog.sym53c8xx | 45 This point had been discussed at the list and the solution 342 (Btw, only problems with Toshiba 3401B had been reported). 530 - Some rewrite of the device detection code. This code had been
|
/linux/Documentation/mm/ |
H A D | unevictable-lru.rst | 230 of VM_LOCKED VMAs that map the page (Rik van Riel had the same idea three years 244 when many processes which had it mlocked were trying to exit. In 5.18, the 511 which had been Copied-On-Write from the file pages now being truncated.
|
H A D | page_migration.rst | 182 5. THP_MIGRATION_SPLIT: A THP was migrated, but not as such: first, the THP had
|
/linux/Documentation/networking/device_drivers/ethernet/3com/ |
H A D | 3c509.rst | 140 These are "mostly harmless" message indicating that the driver had too much
|
/linux/Documentation/admin-guide/media/ |
H A D | faq.rst | 168 see if someone else had a similar problem with your hardware
|
/linux/Documentation/networking/device_drivers/ethernet/dlink/ |
H A D | dl2k.rst | 30 The driver support Linux kernel 2.4.7 later. We had tested it
|
/linux/Documentation/power/ |
H A D | userland-swsusp.rst | 113 suspend image is first created, as though the system had been suspended
|
/linux/Documentation/arch/sparc/ |
H A D | adi.rst | 66 - When a task frees a memory page it had set version tags on, the page
|
/linux/Documentation/admin-guide/ |
H A D | tainted-kernels.rst | 58 this on the machine that had the statements in the logs that were quoted earlier::
|