Searched +full:multi +full:- +full:system (Results 1 – 25 of 1034) sorted by relevance
12345678910>>...42
| /kernel/linux/linux-4.19/drivers/eisa/ |
| D | eisa.ids | 6 # Marc Zyngier <maz@wild-wind.fr.eu.org>
10 ABP0510 "Advansys ABP-510 ISA SCSI Host Adapter"
11 ABP0540 "Advansys ABP-540/542 ISA SCSI Host Adapter"
12 ABP7401 "AdvanSys ABP-740/742 EISA Single Channel SCSI Host Adapter"
13 ABP7501 "AdvanSys ABP-750/752 EISA Dual Channel SCSI Host Adapter"
14 ACC1200 "ACCTON EtherCombo-32 Ethernet Adapter"
15 ACC120A "ACCTON EtherCombo-32 Ethernet Adapter"
18 ACE1010 "ACME Super Fast System Board"
25 ACE7010 "ACME Multi-Function Board"
26 ACR1201 "Acer 1200 486/25 EISA System Board"
[all …]
|
| /kernel/linux/linux-5.10/drivers/eisa/ |
| D | eisa.ids | 6 # Marc Zyngier <maz@wild-wind.fr.eu.org>
10 ABP0510 "Advansys ABP-510 ISA SCSI Host Adapter"
11 ABP0540 "Advansys ABP-540/542 ISA SCSI Host Adapter"
12 ABP7401 "AdvanSys ABP-740/742 EISA Single Channel SCSI Host Adapter"
13 ABP7501 "AdvanSys ABP-750/752 EISA Dual Channel SCSI Host Adapter"
14 ACC1200 "ACCTON EtherCombo-32 Ethernet Adapter"
15 ACC120A "ACCTON EtherCombo-32 Ethernet Adapter"
18 ACE1010 "ACME Super Fast System Board"
25 ACE7010 "ACME Multi-Function Board"
26 ACR1201 "Acer 1200 486/25 EISA System Board"
[all …]
|
| /kernel/linux/linux-4.19/Documentation/block/ |
| D | null_blk.txt | 7 block-layer implementations. It emulates a block device of X gigabytes in size.
10 Single-queue block-layer
11 - Request-based.
12 - Single submission queue per device.
13 - Implements IO scheduling algorithms (CFQ, Deadline, noop).
14 Multi-queue block-layer
15 - Request-based.
16 - Configurable submission queues per device.
17 No block-layer (Known as bio-based)
18 - Bio-based. IO requests are submitted directly to the device driver.
[all …]
|
| /kernel/linux/linux-5.10/arch/parisc/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
62 select HAVE_DYNAMIC_FTRACE if $(cc-option,-fpatchable-function-entry=1,1)
69 The PA-RISC microprocessor is designed by Hewlett-Packard and used
71 and later HP3000 series). The PA-RISC Linux project home page is
85 default "arch/parisc/configs/generic-32bit_defconfig" if !64BIT
86 default "arch/parisc/configs/generic-64bit_defconfig" if 64BIT
119 # unless you want to implement ACPI on PA-RISC ... ;-)
154 that can run on all 32-bit PA CPUs (albeit not optimally fast),
157 Specifying "PA8000" here will allow you to select a 64-bit kernel
163 Select this option for the PCX-L processor, as used in the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| D | null_blk.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 block-layer implementations. It emulates a block device of X gigabytes in size.
15 Multi-queue block-layer
17 - Request-based.
18 - Configurable submission queues per device.
20 No block-layer (Known as bio-based)
22 - Bio-based. IO requests are submitted directly to the device driver.
23 - Directly accepts bio data structure and returns them.
25 All of them have a completion queue for each core in the system.
30 queue_mode=[0-2]: Default: 2-Multi-queue
[all …]
|
| D | blk-mq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Multi-Queue Block IO Queueing Mechanism (blk-mq)
7 The Multi-Queue Block IO Queueing Mechanism is an API to enable fast storage
16 ----------
26 However, with the development of Solid State Drives and Non-Volatile Memories
29 device to the operating system. In order to take advantage of the parallelism
30 in those devices' design, the multi-queue mechanism was introduced.
36 to different CPUs) wanted to perform block IO. Instead of this, the blk-mq API
42 ---------
45 for instance), blk-mq takes action: it will store and manage IO requests to
[all …]
|
| /kernel/linux/linux-5.10/arch/sparc/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 bool "64-bit kernel" if "$(ARCH)" = "sparc"
10 Say yes to build a 64-bit kernel - formerly known as sparc64
11 Say no to build a 32-bit kernel - formerly known as sparc
164 bool "Symmetric multi-processing support"
167 a system with only one CPU, say N. If you have a system with more
170 If you say N here, the kernel will run on uni- and multiprocessor
180 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
233 bool "Support for hot-pluggable CPUs"
237 can be controlled through /sys/devices/system/cpu/cpu#.
[all …]
|
| /kernel/linux/linux-4.19/tools/testing/ktest/examples/ |
| D | test.conf | 12 # machine, which may be different between which system the machine
14 # the machine, where it does not matter which system the machine boots into.
19 CONSOLE = stty -F /dev/ttyS0 115200 parodd; cat /dev/ttyS0
24 # TESTS = patchcheck, randconfig, boot, test, config-bisect, bisect, min-config
30 # Some tests may have more than one test to run. Define MULTI := 1 to run
32 MULTI := 0
34 # In case you want to differentiate which type of system you are testing
46 #PRE_BUILD = patch -p1 < ${THIS_DIR}/fix.patch
52 DO_POST_BUILD := git reset --hard
53 POST_BUILD = ${SSH} 'rm -rf /lib/modules/*-test*'; ${DO_POST_BUILD}
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/ktest/examples/ |
| D | test.conf | 12 # machine, which may be different between which system the machine
14 # the machine, where it does not matter which system the machine boots into.
19 CONSOLE = stty -F /dev/ttyS0 115200 parodd; cat /dev/ttyS0
24 # TESTS = patchcheck, randconfig, boot, test, config-bisect, bisect, min-config
30 # Some tests may have more than one test to run. Define MULTI := 1 to run
32 MULTI := 0
34 # In case you want to differentiate which type of system you are testing
46 #PRE_BUILD = patch -p1 < ${THIS_DIR}/fix.patch
52 DO_POST_BUILD := git reset --hard
53 POST_BUILD = ${SSH} 'rm -rf /lib/modules/*-test*'; ${DO_POST_BUILD}
[all …]
|
| /kernel/linux/linux-4.19/arch/sparc/ |
| D | Kconfig | 2 bool "64-bit kernel" if "$(ARCH)" = "sparc"
9 Say yes to build a 64-bit kernel - formerly known as sparc64
10 Say no to build a 32-bit kernel - formerly known as sparc
163 bool "Symmetric multi-processing support"
164 ---help---
166 a system with only one CPU, say N. If you have a system with more
169 If you say N here, the kernel will run on uni- and multiprocessor
179 See also <file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO
257 bool "Support for hot-pluggable CPUs"
261 can be controlled through /sys/devices/system/cpu/cpu#.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mfd/ |
| D | samsung,sec-core.txt | 1 Binding for Samsung S2M and S5M family multi-function device
4 This is a part of device tree bindings for S2M and S5M family multi-function
8 of multi-function devices which include voltage and current regulators, RTC,
9 charger controller, clock outputs and other sub-blocks. It is interfaced
10 to the host controller using an I2C interface. Each sub-block is usually
11 addressed by the host system using different I2C slave addresses.
14 This document describes bindings for main device node. Optional sub-blocks
15 must be a sub-nodes to it. Bindings for them can be found in:
16 - bindings/regulator/samsung,s2mpa01.txt
17 - bindings/regulator/samsung,s2mps11.txt
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | samsung,sec-core.txt | 1 Binding for Samsung S2M and S5M family multi-function device
4 This is a part of device tree bindings for S2M and S5M family multi-function
8 of multi-function devices which include voltage and current regulators, RTC,
9 charger controller, clock outputs and other sub-blocks. It is interfaced
10 to the host controller using an I2C interface. Each sub-block is usually
11 addressed by the host system using different I2C slave addresses.
14 This document describes bindings for main device node. Optional sub-blocks
15 must be a sub-nodes to it. Bindings for them can be found in:
16 - bindings/regulator/samsung,s2mpa01.txt
17 - bindings/regulator/samsung,s2mps11.txt
[all …]
|
| /kernel/linux/linux-4.19/fs/fscache/ |
| D | Kconfig | 23 multi-CPU system these may be on cachelines that keep bouncing
40 and on a multi-CPU system these may be on cachelines that keep
47 bool "Debug FS-Cache"
|
| /kernel/linux/linux-5.10/fs/fscache/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
24 multi-CPU system these may be on cachelines that keep bouncing
41 and on a multi-CPU system these may be on cachelines that keep
48 bool "Debug FS-Cache"
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/kdump/ |
| D | kdump.rst | 2 Documentation for Kdump - The kexec-based Crash Dumping Solution
11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
12 dump of the system kernel's memory needs to be taken (for example, when
13 the system panics). The system kernel's memory image is preserved across
14 the reboot and is accessible to the dump-capture kernel.
18 a remote system.
23 When the system kernel boots, it reserves a small section of memory for
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
[all …]
|
| /kernel/linux/linux-4.19/Documentation/kdump/ |
| D | kdump.txt | 2 Documentation for Kdump - The kexec-based Crash Dumping Solution
11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
12 dump of the system kernel's memory needs to be taken (for example, when
13 the system panics). The system kernel's memory image is preserved across
14 the reboot and is accessible to the dump-capture kernel.
18 a remote system.
23 When the system kernel boots, it reserves a small section of memory for
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
[all …]
|
| /kernel/linux/linux-4.19/sound/soc/generic/ |
| D | Kconfig | 16 It supports DPCM of multi CPU single Codec system.
24 with OF-graph DT bindings.
32 with OF-graph DT bindings.
33 It supports DPCM of multi CPU single Codec ststem.
|
| /kernel/linux/linux-5.10/drivers/clocksource/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
164 Enable 24-bit TIMER0 and TIMER1 counters in the NPCM7xx architecture,
185 Support for Multi Timer Unit. MTU provides access
187 32-bit free running decrementing counters.
241 bool "Integrator-AP timer driver" if COMPILE_TEST
244 Enables support for the Integrator-AP timer.
277 available on many OMAP-like platforms.
286 It has a 64-bit counter with update rate up to 1000MHz.
287 This counter is accessed via couple of 32-bit memory-mapped registers.
306 bool "Support for 32-bit TIMERn counters in ARC Cores" if COMPILE_TEST
[all …]
|
| /kernel/linux/linux-4.19/drivers/tty/serial/8250/ |
| D | Kconfig | 10 ---help---
16 port for anything. (Note that the Cyclades multi serial port driver
22 non-standard serial ports, since the configuration information will
27 the X window system, try running gpm first.
40 ---help---
50 If you did not notice yet and/or you have userspace from pre-3.7, it
57 ---help---
64 ---help---
78 ---help---
80 system console (the system console is the device which receives all
[all …]
|
| /kernel/linux/linux-5.10/drivers/tty/serial/8250/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
18 port for anything. (Note that the Cyclades multi serial port driver
24 non-standard serial ports, since the configuration information will
29 the X window system, try running gpm first.
52 If you did not notice yet and/or you have userspace from pre-3.7, it
93 system console (the system console is the device which receives all
99 (/dev/tty0) will still be used as the system console by default, but
107 system console.
141 Note that serial ports on NetMos 9835 Multi-I/O cards are handled
162 Say Y here to enable support for 16-bit PCMCIA serial devices,
[all …]
|
| /kernel/linux/linux-4.19/drivers/clocksource/ |
| D | Kconfig | 142 Enable 24-bit TIMER0 and TIMER1 counters in the NPCM7xx architecture,
163 Support for Multi Timer Unit. MTU provides access
165 32-bit free running decrementing counters.
171 Use the Multi Timer Unit as the sched_clock.
225 bool "Integrator-ap timer driver" if COMPILE_TEST
228 Enables support for the Integrator-ap timer.
268 available on many OMAP-like platforms.
293 bool "Support for 32-bit TIMERn counters in ARC Cores" if COMPILE_TEST
297 These are legacy 32-bit TIMER0 and TIMER1 counters found on all ARC cores
302 bool "Support for 64-bit counters in ARC HS38 cores" if COMPILE_TEST
[all …]
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | scaling.txt | 9 multi-processor systems.
24 (multi-queue). On reception, a NIC can send different packets to different
29 generally known as “Receive-side Scaling” (RSS). The goal of RSS and
31 Multi-queue distribution can also be used for traffic prioritization, but
35 and/or transport layer headers-- for example, a 4-tuple hash over
37 implementation of RSS uses a 128-entry indirection table where each entry
45 can be directed to their own receive queue. Such “n-tuple” filters can
46 be configured from ethtool (--config-ntuple).
50 The driver for a multi-queue capable NIC typically provides a kernel
62 commands (--show-rxfh-indir and --set-rxfh-indir). Modifying the
[all …]
|
| /kernel/linux/linux-5.10/tools/power/pm-graph/ |
| D | sleepgraph.8 | 3 sleepgraph \- Suspend/Resume timing analysis
21 Generates output files in subdirectory: suspend-yymmdd-HHMMSS
27 \fB-h\fR
30 \fB-v\fR
33 \fB-verbose\fR
36 \fB-config \fIfile\fR
39 \fB-m \fImode\fR
42 \fB-o \fIname\fR
46 e.g. suspend-{hostname}-{date}-{time}
48 \fB-rtcwake \fIt\fR | off
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/ |
| D | compulab-boards.txt | 1 CompuLab SB-SOM is a multi-module baseboard capable of carrying:
2 - CM-T43
3 - CM-T54
4 - CM-QS600
5 - CL-SOM-AM57x
6 - CL-SOM-iMX7
7 modules with minor modifications to the SB-SOM assembly.
10 - compatible = should be "compulab,sb-som"
12 Compulab CL-SOM-iMX7 is a miniature System-on-Module (SoM) based on
13 Freescale i.MX7 ARM Cortex-A7 System-on-Chip.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-qmss.txt | 3 The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of
4 the main hardware sub system which forms the backbone of the Keystone
5 multi-core Navigator. QMSS consist of queue managers, packed-data structure
9 management of the packet queues. Packets are queued/de-queued by writing or
20 - compatible : Must be "ti,keystone-navigator-qmss".
21 : Must be "ti,66ak2g-navss-qm" for QMSS on K2G SoC.
22 - clocks : phandle to the reference clock for this device.
23 - queue-range : <start number> total range of queue numbers for the device.
24 - linkram0 : <address size> for internal link ram, where size is the total
26 - linkram1 : <address size> for external link ram, where size is the total
[all …]
|
12345678910>>...42