Searched +full:alternative +full:- +full:b (Results 1 – 25 of 54) sorted by relevance
123
| /Documentation/networking/pse-pd/ |
| D | pse-pi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 eight-pin modular jack, commonly known as the Ethernet RJ45 port. This
14 ---------------------------
19 - Section "33.2.3 PI pin assignments" covers the pin assignments for PoE
21 - Section "145.2.4 PSE PI" addresses the configuration for PoE systems that
25 -------------------------------
31 two pairs of wires, SPE operates on a simpler model due to its single-pair
32 design. As a result, the complexities of choosing between alternative pin
33 assignments for power delivery, as described in the PSE PI for multi-pair
37 --------------------
[all …]
|
| /Documentation/devicetree/bindings/net/pse-pd/ |
| D | pse-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/pse-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 power over twisted pair/ethernet cable. The ethernet-pse nodes should be
12 used to describe PSE controller and referenced by the ethernet-phy node.
15 - Oleksij Rempel <o.rempel@pengutronix.de>
16 - Kory Maincent <kory.maincent@bootlin.com>
20 pattern: "^ethernet-pse(@.*|-([0-9]|[1-9][0-9]+))?$"
22 "#pse-cells":
[all …]
|
| D | microchip,pd692x0.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/microchip,pd692x0.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Kory Maincent <kory.maincent@bootlin.com>
13 - $ref: pse-controller.yaml#
18 - microchip,pd69200
19 - microchip,pd69210
20 - microchip,pd69220
40 "#address-cells":
[all …]
|
| D | ti,tps23881.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/ti,tps23881.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Kory Maincent <kory.maincent@bootlin.com>
13 - $ref: pse-controller.yaml#
18 - ti,tps23881
23 '#pse-cells':
26 reset-gpios:
38 "#address-cells":
[all …]
|
| /Documentation/devicetree/bindings/connector/ |
| D | usb-connector.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/connector/usb-connector.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
20 - enum:
21 - usb-a-connector
22 - usb-b-connector
23 - usb-c-connector
25 - items:
[all …]
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
13 # use "select". For instance it means if a driver A and driver B share the same
16 # driver B.
23 # The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
36 # of select refer to Documentation/kbuild/Kconfig.select-break
42 # "select FW_LOADER" [0], in the end the simple alternative solution to this
45 # [0] https://lore.kernel.org/r/1432241149-8762-1-git-send-email-mcgrof@do-not-panic.com
|
| /Documentation/arch/x86/ |
| D | topology.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 The architecture-agnostic topology definitions are in
12 Documentation/admin-guide/cputopology.rst. This file holds x86-specific
17 Needless to say, code should use the generic functions - this file is *only*
35 - packages
36 - cores
37 - threads
48 Package-related topology information in the kernel:
50 - topology_num_threads_per_package()
54 - topology_num_cores_per_package()
[all …]
|
| D | cpuinfo.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 represents an ill-fated attempt from long time ago to put feature flags
18 because userspace doesn't care about them - glibc et al already use
21 And even if it doesn't show a particular feature flag - although the CPU
23 said CPU supports CPUID faulting - userspace can simply probe for the
56 On the other hand, a new kernel running on non-VAES hardware would also
83 ------------------------------------------------------------------
92 b: Flags can be from scattered CPUID-based features.
93 ----------------------------------------------------
95 software-defined values. Still, CPUID needs to be queried to determine
[all …]
|
| /Documentation/admin-guide/blockdev/ |
| D | zram.rst | 2 zram: Compressed RAM-based block devices
8 The zram module creates RAM-based block devices named /dev/zram<id>
20 There are several ways to configure and manage zram device(-s):
23 b) using zramctl utility, provided by util-linux (util-linux@vger.kernel.org).
28 In order to get a better idea about zramctl please consult util-linux
29 documentation, zramctl man-page or `zramctl --help`. Please be informed
30 that zram maintainers do not develop/maintain util-linux or zramctl, should
31 you have any questions please contact util-linux@vger.kernel.org
45 -EBUSY an attempt to modify an attribute that cannot be changed once
47 -ENOMEM zram was not able to allocate enough memory to fulfil your
[all …]
|
| /Documentation/networking/ |
| D | filter.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 .. _networking-filter:
10 ------
17 ------------
24 BPF allows a user-space program to attach a filter onto any socket and
49 The biggest user of this construct might be libpcap. Issuing a high-level
50 filter command like `tcpdump -i em1 port 22` passes through the libpcap
52 via SO_ATTACH_FILTER to the kernel. `tcpdump -i em1 port 22 -ddd`
57 qdisc layer, SECCOMP-BPF (SECure COMPuting [1]_), and lots of other places
60 .. [1] Documentation/userspace-api/seccomp_filter.rst
[all …]
|
| D | nf_flowtable.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 --------
28 n-tuple selectors: layer 2 protocol encapsulation (VLAN and PPPoE), layer 3
35 new alternative forwarding path via policy.
51 _________ __________ --------- _____\/_____
53 --> ingress ---> prerouting ---> |decision| | postrouting |--> neigh_xmit
54 \_________/ \__________/ ---------- \____________/ ^
58 __\/___ | | forward |------------ |
59 |-----| | \_________/ |
60 |-----| | 'flow offload' rule |
[all …]
|
| /Documentation/arch/powerpc/ |
| D | dexcr.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
11 PowerPC ISA 3.1B (Power10) that allows per-cpu control over several dynamic
13 branch target prediction) and enabling return-oriented programming (ROP)
24 A hypervisor-privileged SPR that can control aspects for the hypervisor and
27 An optional ultravisor-privileged SPR that can control aspects for the ultravisor.
30 provides a non-privileged read-only view of the userspace DEXCR aspects.
31 There is also an SPR that provides a read-only view of the hypervisor enforced
40 -----
52 .. flat-table::
53 :header-rows: 1
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_osd.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later OR GPL-2.0
14 The DVB OSD device controls the OnScreen-Display of the AV7110 based
15 DVB-cards with hardware MPEG2 decoder. It can be accessed through
20 The OSD is not a frame-buffer like on many other cards.
22 The color-depth is limited depending on the memory size installed.
31 -----------
36 .. code-block:: c
39 /* All functions return -2 on "not open" */
67 .. note:: All functions return -2 on "not open"
69 .. flat-table::
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 30 - The kernel probes are the most generic. The code can be redirected by
33 - The function tracer calls the code from a predefined location that is
35 compiler using the '-pg' gcc option.
37 - Livepatching typically needs to redirect the code at the very beginning
45 is probed, see CONFIG_KPROBES_ON_FTRACE. Also an alternative function from
74 The aim is to define a so-called consistency model. It attempts to define
79 kpatch: it uses kGraft's per-task consistency and syscall barrier
83 Patches are applied on a per-task basis, when the task is deemed safe to
108 a) Patching I/O-bound user tasks which are sleeping on an affected
111 b) Patching CPU-bound user tasks. If the task is highly CPU-bound
[all …]
|
| /Documentation/isdn/ |
| D | interface_capi.rst | 9 COMMON-ISDN-API (CAPI) is an application programming interface standard used
74 ----------------------
78 the following non-private fields, all to be set by the driver before calling
82 the name of the driver, as a zero-terminated ASCII string
84 the revision number of the driver, as a zero-terminated ASCII string
87 -------------------
94 It contains the following non-private fields:
106 the name of the controller, as a zero-terminated ASCII string
109 the name of the driver, as a zero-terminated ASCII string
154 non-zero (error) value then ownership of the skb returns to the caller
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-mic | 8 PCIe form factor add-in Coprocessor card based on the Intel Many
26 MIC device. For example - "x100"
34 MIC device. For example - "A0" or "B0"
99 self-bootable machines. When read, this entry provides
135 a) linux - Boot a Linux image.
136 b) flash - Boot an image for flash updates.
177 alternative means such as a network ping. This setting is
|
| /Documentation/RCU/ |
| D | checklist.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 0. Is RCU being applied to a read-mostly situation? If the data
18 tool for the job. Yes, RCU does reduce read-side overhead by
19 increasing write-side overhead, which is exactly why normal uses
27 Yet another exception is where the low real-time latency of RCU's
28 read-side primitives is critically important.
33 counter-intuitive situation where rcu_read_lock() and
44 b. atomic operations, or
47 If you choose #b, be prepared to describe how you have handled
49 them -- even x86 allows later loads to be reordered to precede
[all …]
|
| /Documentation/arch/arm/ |
| D | booting.rst | 9 The following documentation is relevant to 2.4.18-rmk6 and beyond.
28 ---------------------------
44 -----------------------------
56 As an alternative, the boot loader can pass the relevant 'console='
60 Documentation/admin-guide/kernel-parameters.rst.
64 --------------------------
69 MANDATORY except for DT-only platforms
75 value to the kernel. (see linux/arch/arm/tools/mach-types). This
78 For DT-only platforms, the machine type will be determined by device
83 ------------------
[all …]
|
| /Documentation/bpf/ |
| D | classic_vs_extended.rst | 12 - Number of registers increase from 2 to 10:
15 new layout extends this to be 10 internal registers and a read-only frame
16 pointer. Since 64-bit CPUs are passing arguments to functions via registers
17 the number of args from eBPF program to in-kernel function is restricted
18 to 5 and one register is used to accept return value from an in-kernel
20 sparcv9/mips64 have 7 - 8 registers for arguments; x86_64 has 6 callee saved
25 64-bit architectures.
27 On 32-bit architectures JIT may map programs that use only 32-bit arithmetic
30 R0 - R5 are scratch registers and eBPF program needs spill/fill them if
33 call predefined in-kernel functions, though.
[all …]
|
| /Documentation/admin-guide/thermal/ |
| D | intel_powerclamp.rst | 6 - Arjan van de Ven <arjan@linux.intel.com>
7 - Jacob Pan <jacob.jun.pan@linux.intel.com>
12 - Goals and Objectives
15 - Idle Injection
16 - Calibration
19 - Effectiveness and Limitations
20 - Power vs Performance
21 - Scalability
22 - Calibration
23 - Comparison with Alternative Techniques
[all …]
|
| /Documentation/block/ |
| D | bfq-iosched.rst | 5 BFQ is a proportional-share I/O scheduler, with some extra
6 low-latency capabilities. In addition to cgroups support (blkio or io
9 - BFQ guarantees a high system and application responsiveness, and a
10 low latency for time-sensitive applications, such as audio or video
12 - BFQ distributes bandwidth, not just time, among processes or
19 goal, for a given device, is to achieve the maximum-possible
20 throughput at all times, then do switch off all low-latency heuristics
25 As every I/O scheduler, BFQ adds some overhead to per-I/O-request
27 single-lock-protected, per-request processing time of BFQ---i.e., the
29 completion hooks---is, e.g., 1.9 us on an Intel Core i7-2760QM@2.40GHz
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | exporting.rst | 7 --------
10 point. Local applications have a reference-counted hold on suitable
14 different way to refer to a particular dentry. As the alternative
16 server-reboot (among other things, though these tend to be the most
32 -------------
48 2. The dcache must be prepared for a newly found (via ->lookup) directory
49 to already have a (non-connected) dentry, and must be able to move
51 ->lookup). This is particularly needed for directories as
68 without losing DCACHE_DISCONNECTED - that flag is only cleared when
75 b. A primitive for creation of secondary roots - d_obtain_root(inode).
[all …]
|
| /Documentation/translations/it_IT/process/ |
| D | 7.AdvancedTopics.rst | 1 .. include:: ../disclaimer-ita.rst
17 -----------------------------
24 Oggigiorno, ci sono diverse alternative libere a BitKeeper. Per il meglio o il
38 https://git-scm.com/
40 https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
52 *index*, *fast-forward merge*, *push* e *pull*, *detached head*, eccetera.
62 eseguire git-daemon è relativamente semplice . Altrimenti, iniziano a
74 solo quando sono complete e pronte ad essere consegnate - non prima.
103 un ramo già pubblicato. Un esempio è linux-next dove le patch vengono
118 solo nei momenti di rilascio (per esempio gli -rc del ramo principale).
[all …]
|
| /Documentation/filesystems/ |
| D | overlayfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
17 ---------------
25 While directories will report an st_dev from the overlay-filesystem,
26 non-directory objects may report an st_dev from the lower filesystem or
29 over the lifetime of a non-directory object. Many applications and
48 The "xino" feature can be enabled with the "-o xino=on" overlay mount option.
51 the lifetime of the filesystem. The "-o xino=auto" overlay mount option
60 +--------------+------------+------------+-----------------+----------------+
[all …]
|
| /Documentation/process/ |
| D | coding-style.rst | 19 --------------
31 Now, some people will claim that having 8-character indentations makes
33 80-character terminal screen. The answer to that is that if you need
37 In short, 8-char indents make things easier to read, and have the added
43 instead of ``double-indenting`` the ``case`` labels. E.g.:
45 .. code-block:: c
67 .. code-block:: c
74 .. code-block:: c
81 .. code-block:: c
99 ----------------------------------
[all …]
|
123