| /openbmc/linux/Documentation/locking/ |
| H A 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.)
|
| /openbmc/docs/designs/ |
| H A D | expired-password.md | 179 - Unique password per machine. That approach requires additional effort, for
184 through the BMC's host system or via the BMC's serial console. That approach
187 - Disable network access by default. That approach requires another BMC access
191 SSH client certificate. That approach suffers from the same limitations as a
195 jumper, or signing in via a serial cable. That approach is not standard.
198 That approach requires the customer have an LDAP (or similar) server. Also,
203 this condition. That approach doesn't solve the problem and burdens BMC
|
| H A D | uart-mux-support.md | 141 Taking a connection-based approach to setting the mux state (2.3) will cause the
169 A further concern for the out-of-band command approach is its interactions with
176 With the out-of-band command approach these components have to choose between:
278 The second approach is quite explicit - directly representing the mux state
287 The first approach doesn't have this limitation. However, it does have the
316 Taking this approach avoids adding a new endpoint ABI to obmc-console and
386 provide a similar approach for specifying the mux GPIOs to that used by [the
|
| H A D | bmc-reboot-cause-update.md | 19 In the current approach, the only defined reboot causes are **WDIOF_EXTERN1**
94 In the original approach, **WDIOF_CARDRESET** was used to represent a **POR**
|
| H A D | multi-host-postcode.md | 222 **phosphor-post-code-manager single process approach**
225 this approach, all D-Bus handling will taken care by the single process.
228 where multi-service approach is used.
230 Multi-service approach is more scalable to handle multi-host than the single
|
| /openbmc/linux/Documentation/bpf/ |
| H A 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
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A 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
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-pyparsing_3.2.1.bb | 2 DESCRIPTION = "The pyparsing module is an alternative approach to creating \
3 and executing simple grammars, vs. the traditional lex/yacc approach, or \
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | ci-definitions.rst.inc | 57 testing focuses on interactions, use case-based testing is a practical approach
108 A Practitioner’s Approach. p. 48, 376, 378, 381.
110 A Practitioner’s Approach. p. 388.
112 A Practitioner’s Approach. Software Engineering, p. 377.
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | dvbproperty.rst | 23 So, the legacy union/struct based approach was deprecated, in favor
24 of a properties set approach. On such approach,
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp.md | 84 - A userspace-based approach, using a core library, plus a demultiplexing
89 - A kernel-based approach, using a sockets API for client and server
90 applications. This approach is recommended for new designs, and is described
|
| H A D | mctp-userspace.md | 126 drawback of this approach is that this single process needs to implement all
130 frameworks used, etc). Also, this single-process approach would likely need more
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A 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
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | kasan.txt | 38 One approach is just to give up on inline instrumentation. This way boot-time
41 current approach.
|
| /openbmc/linux/include/linux/platform_data/ |
| H A D | davinci_asp.h | 50 * SYMMETRICAL APPROACH:
59 * ACCURATE CLOCK APPROACH:
|
| /openbmc/linux/kernel/trace/ |
| H A 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
|
| /openbmc/linux/Documentation/filesystems/ |
| H A 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
|
| H A D | inotify.rst | 78 Why the system call approach?
87 family of system calls because that is the preferred approach for new kernel
|
| /openbmc/linux/Documentation/arch/arm/nwfpe/ |
| H A 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
|
| /openbmc/linux/net/ipv4/ |
| H A 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.
|
| /openbmc/phosphor-pid-control/pid/ |
| H A D | pidloop.cpp | 95 * Another approach would be to start all sensors in worst-case in pidControlLoop()
98 * approach. in pidControlLoop()
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-fs-f2fs | 26 gc_idle = 1 will select the Cost Benefit approach & setting
27 gc_idle = 2 will select the greedy approach & setting
28 gc_idle = 3 will select the age-threshold based approach.
311 GC approach and turns SSR mode on.
314 little bit aggressively. always uses cost benefit GC approach,
315 and will override age-threshold GC approach if ATGC is enabled
319 always uses cost benefit GC approach, and will override
320 age-threshold GC approach if ATGC is enabled at the same time.
|
| /openbmc/u-boot/doc/ |
| H A D | README.xtensa | 57 Windowed ABI presents unique difficulties with the approach based on
68 be passed in registers. The most efficient approach is to have the jump
|
| /openbmc/docs/architecture/code-update/ |
| H A D | emmc-storage-design.md | 97 partition. This approach allows the re-use of the existing code update
98 interfaces, since the static approach does not currently support storing two
100 existing U-Boot environment approach.
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A 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
|