Searched full:approach (Results 1 – 25 of 997) sorted by relevance
12345678910>>...40
| /kernel/linux/linux-6.6/Documentation/locking/ |
| D | robust-futexes.rst | 54 To solve this problem, the traditional approach was to extend the vma
56 robust futexes attached to this area'. This approach requires 3 new
59 they have a robust_head set. This approach has two fundamental problems
63 approach had been pending for years, but they are still not completely
86 New approach to robust futexes
89 At the heart of this new approach there is a per-thread private list of
124 Key differences of this userspace-list based approach, compared to the
157 I have also measured an approach where glibc does the lock notification
164 approach scales nicely.)
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | robust-futexes.rst | 54 To solve this problem, the traditional approach was to extend the vma
56 robust futexes attached to this area'. This approach requires 3 new
59 they have a robust_head set. This approach has two fundamental problems
63 approach had been pending for years, but they are still not completely
86 New approach to robust futexes
89 At the heart of this new approach there is a per-thread private list of
124 Key differences of this userspace-list based approach, compared to the
157 I have also measured an approach where glibc does the lock notification
164 approach scales nicely.)
|
| /kernel/linux/linux-6.6/Documentation/bpf/ |
| D | ringbuf.rst | 41 ``BPF_MAP_TYPE_HASH_OF_MAPS`` addresses this with current approach.
44 approach would be an overkill.
46 Another approach could introduce a new concept, alongside BPF map, to represent
48 with lookup/update/delete operations. This approach would add a lot of extra
52 additional benefits over the approach of using a map. ``BPF_MAP_TYPE_RINGBUF``
56 The approach chosen has an advantage of re-using existing BPF map
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | ringbuf.rst | 41 ``BPF_MAP_TYPE_HASH_OF_MAPS`` addresses this with current approach.
44 approach would be an overkill.
46 Another approach could introduce a new concept, alongside BPF map, to represent
48 with lookup/update/delete operations. This approach would add a lot of extra
52 additional benefits over the approach of using a map. ``BPF_MAP_TYPE_RINGBUF``
56 The approach chosen has an advantage of re-using existing BPF map
|
| /kernel/linux/linux-6.6/tools/memory-model/Documentation/ |
| D | simple.txt | 39 This approach is called "code locking".
62 takes this approach for much of its grace-period processing and also
77 This approach delegates any LKMM worries to the library maintainer.
98 The poster boy for this approach is the hash table, where placing a lock
114 a single-threaded approach while providing excellent performance and
120 must be used to protect this global view. This is the approach taken
207 or modifying the variable. This approach guarantees that code prior
|
| /kernel/linux/linux-5.10/tools/memory-model/Documentation/ |
| D | simple.txt | 39 This approach is called "code locking".
62 takes this approach for much of its grace-period processing and also
77 This approach delegates any LKMM worries to the library maintainer.
98 The poster boy for this approach is the hash table, where placing a lock
114 a single-threaded approach while providing excellent performance and
120 must be used to protect this global view. This is the approach taken
208 or modifying the variable. This approach guarantees that code prior
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/dvb/ |
| D | dvbproperty.rst | 23 So, the legacy union/struct based approach was deprecated, in favor
24 of a properties set approach. On such approach,
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | dvbproperty.rst | 23 So, the legacy union/struct based approach was deprecated, in favor
24 of a properties set approach. On such approach,
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | README | 29 This approach for testing switch ASICs has several advantages over the
38 not always available. With the VRF-based approach one merely needs to
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/forwarding/ |
| D | README | 29 This approach for testing switch ASICs has several advantages over the
38 not always available. With the VRF-based approach one merely needs to
|
| /kernel/linux/linux-6.6/Documentation/powerpc/ |
| D | kasan.txt | 38 One approach is just to give up on inline instrumentation. This way boot-time
41 current approach.
|
| /kernel/linux/linux-6.6/kernel/trace/ |
| D | trace_preemptirq.c | 39 * and lockdep uses a staged approach which splits the lockdep hardirq
70 * and lockdep uses a staged approach which splits the lockdep hardirq
|
| /kernel/linux/linux-6.6/include/linux/platform_data/ |
| D | davinci_asp.h | 50 * SYMMETRICAL APPROACH:
59 * ACCURATE CLOCK APPROACH:
|
| /kernel/linux/linux-5.10/kernel/trace/ |
| D | trace_preemptirq.c | 25 * and lockdep uses a staged approach which splits the lockdep hardirq
58 * and lockdep uses a staged approach which splits the lockdep hardirq
|
| /kernel/linux/linux-5.10/include/linux/platform_data/ |
| D | davinci_asp.h | 58 * SYMMETRICAL APPROACH:
67 * ACCURATE CLOCK APPROACH:
|
| /kernel/linux/linux-5.10/net/ipv4/ |
| D | tcp_rate.c | 14 * at which packets were acknowledged. However, the approach of using only the
28 * deliberately avoids using the inter-packet spacing approach because that
29 * approach requires a large number of samples and sophisticated filtering.
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | ubifs-authentication.rst | 36 This document describes an approach to get file contents _and_ full metadata
274 Using this approach only UBIFS index nodes and the master node are changed to
396 has a different approach of encryption policies per directory, there can be
398 UBIFS authentication on the other hand has an all-or-nothing approach in the
407 fscrypt approach has shown its flaws and the userspace API will eventually
418 approach is similar to the approach proposed for fscrypt encryption policy v2
|
| D | inotify.rst | 78 Why the system call approach?
87 family of system calls because that is the preferred approach for new kernel
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | ubifs-authentication.rst | 36 This document describes an approach to get file contents _and_ full metadata
274 Using this approach only UBIFS index nodes and the master node are changed to
396 has a different approach of encryption policies per directory, there can be
398 UBIFS authentication on the other hand has an all-or-nothing approach in the
407 fscrypt approach has shown its flaws and the userspace API will eventually
418 approach is similar to the approach proposed for fscrypt encryption policy v2
|
| D | inotify.rst | 78 Why the system call approach?
87 family of system calls because that is the preferred approach for new kernel
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/nwfpe/ |
| D | todo.rst | 25 There are a couple of ways to approach the implementation of these. One
31 Another approach, which I know little about is CORDIC. This stands for
|
| /kernel/linux/linux-5.10/Documentation/arm/nwfpe/ |
| D | todo.rst | 25 There are a couple of ways to approach the implementation of these. One
31 Another approach, which I know little about is CORDIC. This stands for
|
| /kernel/linux/linux-6.6/net/ipv4/ |
| D | tcp_rate.c | 14 * at which packets were acknowledged. However, the approach of using only the
28 * deliberately avoids using the inter-packet spacing approach because that
29 * approach requires a large number of samples and sophisticated filtering.
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | no_hz.rst | 21 approach, and should be the default.
38 there are some situations where this old-school approach is still the
39 right approach, for example, in heavy workloads with lots of tasks
192 Another approach is to offload RCU callback processing to "rcuo" kthreads
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
| D | xilinx.txt | 17 The new approach is to export the parameters into the device tree and
89 That covers the general approach to binding xilinx IP cores into the
|
12345678910>>...40