| /linux/Documentation/locking/ |
| H A D | pi-futex.rst | 34 can see it in the kernel [which is a quite complex program in itself],
67 [this is a quite common scenario for most non-trivial RT applications],
79 mutexes involves no kernel work at all - they behave quite similarly to
114 there is no prior 'registration' of a PI-futex. [which is not quite
|
| /linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 6 (LKMM) is quite complex, with subtle differences in code often having
9 The options near the beginning of this list are quite simple. The idea
79 In the kernel, what is the "library"? Quite a bit. It includes the
194 Reading code using these primitives is often also quite helpful.
240 It can be quite tempting to use plain C-language accesses for lockless
242 possible and quite common in the Linux kernel, it does require a
|
| H A D | recipes.txt | 65 about it too hard. And the basic rule is indeed quite simple: Any CPU that
153 Counter-intuitive though it might be, it is quite possible to have
245 Use of rcu_assign_pointer() and rcu_dereference() is quite similar to the
357 absence of any ordering it is quite possible that this may happen, as
|
| /linux/Documentation/admin-guide/ |
| H A D | cpu-load.rst | 21 In most cases the ``/proc/stat`` information reflects the reality quite
44 (only to be awaken quite soon)
52 will lead to quite erratic information inside ``/proc/stat``::
|
| H A D | reporting-issues.rst | 290 distributors are quite distant from the official Linux kernel as distributed by
294 Most of these vendor kernels are quite unsuitable for reporting issues to the
310 issue in question. Your chances are quite good if the distributor applied only
558 various issues in one report also makes it quite difficult for others to tear
600 it. Quite a few programmers for example only care for just one driver, for
753 quite a few other lists miss a way to search the archives. In those cases use a
767 or even more time can save you and others quite a lot of time and trouble.
822 quite busy then and might have no spare time to deal with issue reports. It's
823 also quite possible that one of the many changes applied during the merge
860 But you are in luck if you are using a popular Linux distribution: for quite a
[all …]
|
| /linux/Documentation/filesystems/ |
| H A D | romfs.rst | 7 This is a quite dumb, read only filesystem, mainly for initial RAM
42 filesystems, like the quite large ext2fs module, which can then be
55 bytes. This is quite rare however, since most file names are longer
87 the source. This algorithm was chosen because although it's not quite
184 - Compression might be an useful feature, but memory is quite a
|
| H A D | path-lookup.rst | 66 calls interpret it quite differently (e.g. some create it, some do
69 exist, it could be "``.``" or "``..``" which are handled quite differently
90 "everything else" quite separately from the final component, and
599 It is in many ways similar to REF-walk and the two share quite a bit
608 quite different from traditional locking, so we will spend a little extra
735 it for that too, but for quite a bit more.
858 Taking a reference on those pointers is not quite as simple as just
952 Handling directories is quite straightforward: the new directory
980 and, given the second reason for restriction, quite sufficient.
1039 uses to access the dcache and icache (inode cache) safely are quite
[all …]
|
| H A D | ubifs.rst | 38 It should be quite obvious why UBIFS is very different to traditional
63 it possible to fit quite a lot of data to the flash.
|
| /linux/arch/arm/mach-omap2/ |
| H A D | cm2xxx.h | 9 * The CM hardware modules on the OMAP2/3 are quite similar to each
10 * other. The CM modules/instances on OMAP4 are quite different, so
|
| H A D | cm3xxx.h | 9 * The CM hardware modules on the OMAP2/3 are quite similar to each
10 * other. The CM modules/instances on OMAP4 are quite different, so
|
| H A D | cm2xxx_3xxx.h | 9 * The CM hardware modules on the OMAP2/3 are quite similar to each
10 * other. The CM modules/instances on OMAP4 are quite different, so
|
| /linux/tools/objtool/arch/x86/ |
| H A D | special.c | 91 * for the function, but that would require redesigning the code quite a
102 * As of GCC 7 there are quite a few more of these and the 'in between' code
154 * Use of RIP-relative switch jumps is quite rare, and in arch_find_switch_table()
|
| /linux/fs/netfs/ |
| H A D | Kconfig | 20 execution as there are a quite a few stats gathered, and on a
55 execution as there are a quite a few stats gathered, and on a
|
| /linux/drivers/leds/ |
| H A D | TODO | 28 i/o port is really quite different from camera flash LED, which is
50 RGB LEDs are quite common, and it would be good to be able to turn LED
|
| /linux/arch/sh/drivers/pci/ |
| H A D | fixups-dreamcast.c | 77 * The interrupt routing semantics here are quite trivial. in pcibios_map_platform_irq()
81 * interrupt. Keeps routing quite simple, doesn't it? in pcibios_map_platform_irq()
|
| /linux/Documentation/networking/ |
| H A D | arcnet.rst | 51 individual chipset drivers, and the source files aren't quite so packed with
269 quite the way Linux does (actually, it doesn't multitask AT ALL) but
302 interface quite nicely with TCP/IP-based WfWg or Lan Manager
366 smaller than the Internet "requirement," so it's quite
494 It's quite fortunate that I set things up like this the first time (cough
551 which is obviously quite big.
|
| /linux/kernel/rcu/ |
| H A D | Kconfig.debug | 123 containing only lockless code. After all, it is quite possible
150 NO_HZ. These checks have proven quite helpful in detecting
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-dv.rst | 85 standard correctly (unfortunately quite common for HDMI and DVI-D).
144 standard correctly (unfortunately quite common for HDMI and DVI-D).
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | via-velocity.txt | 10 devices quite often set this data in uboot and do not provide an eeprom.
|
| /linux/drivers/media/i2c/ |
| H A D | tea6415c.h | 5 /* the tea6415c's design is quite brain-dead. although there are
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | apq8094-sony-xperia-kitakami-karin_windy.dts | 8 /* As the names may imply, there is quite a bunch of duplication there. */
|
| /linux/Documentation/process/ |
| H A D | 4.Coding.rst | 144 slow execution dramatically. Inline functions, as a rule, should be quite
242 potential errors. Quite often, these warnings point to real problems.
272 There are quite a few other debugging options, some of which will be
317 problems. Quite a few "semantic patches" for the kernel have been packaged
|
| /linux/tools/include/nolibc/ |
| H A D | std.h | 10 /* Declare a few quite common macros and types that usually are in stdlib.h,
|
| /linux/arch/arm64/boot/dts/allwinner/ |
| H A D | sun50i-a64-pinephone-1.1.dts | 19 * also varries quite a bit between individual boards, so the lowest
|
| /linux/arch/arm/boot/compressed/ |
| H A D | head-xscale.S | 23 add r3, r2, #0x10000 @ 64 kb is quite enough...
|