Searched refs:accelerated (Results 1 – 25 of 36) sorted by relevance
12
| /Linux-v5.4/drivers/crypto/ |
| D | Kconfig | 112 This is the s390 hardware accelerated implementation of the
123 This is the s390 hardware accelerated implementation of the
133 This is the s390 hardware accelerated implementation of the
143 This is the s390 hardware accelerated implementation of the
153 This is the s390 hardware accelerated implementation of the
163 This is the s390 hardware accelerated implementation of the
175 This is the s390 hardware accelerated implementation of the
178 As of z990 the ECB and CBC mode are hardware accelerated.
179 As of z196 the CTR mode is hardware accelerated.
187 This is the s390 hardware accelerated implementation of the
[all …]
|
| /Linux-v5.4/arch/arm/crypto/ |
| D | Kconfig | 108 tristate "PMULL-accelerated GHASH using NEON/ARMv8 Crypto Extensions"
130 tristate "NEON accelerated ChaCha stream cipher algorithms"
136 tristate "NEON accelerated NHPoly1305 hash function (for Adiantum)"
|
| /Linux-v5.4/Documentation/networking/ |
| D | failover.rst | 16 This enables paravirtual drivers to use a VF as an accelerated low latency
|
| D | net_failover.rst | 28 virtio-net accelerated datapath: STANDBY mode
31 net_failover enables hypervisor controlled accelerated datapath to virtio-net
|
| D | gtp.txt | 64 data plane is accelerated inside the kernel.
67 kernel accelerated path, while the GTP Control Plane goes to
|
| D | scaling.rst | 353 Accelerated RFS is to RFS what RSS is to RPS: a hardware-accelerated load
361 To enable accelerated RFS, the networking stack calls the
|
| /Linux-v5.4/Documentation/fb/ |
| D | vesafb.rst | 20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
|
| D | lxfb.rst | 37 XF68_FBDev should generally work fine, but it is non-accelerated.
|
| D | gxfb.rst | 36 XF68_FBDev should generally work fine, but it is non-accelerated.
|
| D | matroxfb.rst | 93 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
97 Running another (accelerated) X-Server like XF86_SVGA works too. But (at least)
99 head, not even talking about second). Running XFree86 4.x accelerated mga
209 non-accelerated mode (`noaccel` or `fbset -accel false`), software
415 + secondary head is not accelerated. There were bad problems with accelerated
435 + secondary head is not accelerated.
|
| D | aty128fb.rst | 42 XF68_FBDev should generally work fine, but it is non-accelerated. As of
|
| D | tridentfb.rst | 15 All families are accelerated. Only PCI/AGP based cards are supported,
|
| /Linux-v5.4/Documentation/devicetree/bindings/leds/ |
| D | leds-spi-byte.txt | 13 accelerated blinking) might can be supported too.
|
| /Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | Kconfig | 43 bool "Mellanox MLX5 ethernet accelerated receive flow steering (ARFS) support"
47 Mellanox MLX5 ethernet hardware-accelerated receive flow steering support,
|
| /Linux-v5.4/drivers/video/fbdev/omap/ |
| D | Kconfig | 60 memory, or don't use any of the accelerated features.
|
| /Linux-v5.4/drivers/net/ethernet/sfc/ |
| D | Kconfig | 54 features, allowing accelerated network performance in
|
| /Linux-v5.4/drivers/soc/tegra/ |
| D | Kconfig | 86 and providing 256 CUDA cores. It supports hardware-accelerated en-
|
| /Linux-v5.4/Documentation/scsi/ |
| D | cxgb3i.txt | 81 4. To direct open-iscsi traffic to go through cxgb3i's accelerated path,
|
| /Linux-v5.4/drivers/infiniband/hw/i40iw/ |
| D | i40iw_cm.h | 338 bool accelerated; member
|
| D | i40iw_cm.c | 1863 !cm_node->accelerated) { in i40iw_dec_refcnt_listen()
2303 if (!cm_node->accelerated && cm_node->accept_pend) { in i40iw_rem_ref_cm_node()
3762 cm_node->accelerated = true; in i40iw_accept()
4123 cm_node->accelerated = true; in i40iw_cm_event_connected()
|
| /Linux-v5.4/Documentation/networking/device_drivers/mellanox/ |
| D | mlx5.rst | 42 | Enables Hardware-accelerated receive flow steering (arfs) support, and ntuple filtering.
75 | Requires CONFIG_MLX5_CORE_EN to provide an accelerated interface for the rdma
|
| /Linux-v5.4/crypto/ |
| D | Kconfig | 514 the SoC in question has accelerated CBC but not XTS, making CBC
515 combined with ESSIV the only feasible mode for h/w accelerated
577 support CRC32C implementation using hardware accelerated CRC32
619 CRC32 PCLMULQDQ implementation using hardware accelerated PCLMULQDQ
656 accelerated PCLMULQDQ instruction. This option will create
870 This is the powerpc hardware accelerated implementation of the
1012 tristate "GHASH hash function (CLMUL-NI accelerated)"
1016 This is the x86_64 CLMUL-NI accelerated implementation of
|
| /Linux-v5.4/drivers/video/fbdev/ |
| D | Kconfig | 45 (e.g. an accelerated X server) and that are not frame buffer
82 (accelerated) version.
89 This is used by drivers that don't provide their own (accelerated)
98 (accelerated) version.
114 (accelerated) version and the framebuffer is in system RAM.
121 This is used by drivers that don't provide their own (accelerated)
130 (accelerated) version and the framebuffer is in system RAM.
1178 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1654 bool "VT8500/WM8xxx accelerated raster ops support"
1657 This adds support for accelerated raster operations on the
|
| /Linux-v5.4/drivers/net/ethernet/stmicro/stmmac/ |
| D | Kconfig | 79 will behave like standard non-accelerated ethernet interfaces.
|
| /Linux-v5.4/Documentation/leds/ |
| D | leds-class.rst | 150 Hardware accelerated blink of LEDs
|
12
