/linux/arch/s390/crypto/ |
H A D | Kconfig | 83 As of z9 the ECB and CBC modes are hardware accelerated 86 As of z10 the ECB and CBC modes are hardware accelerated 89 As of z196 the CTR mode is hardware accelerated for all AES 90 key sizes and XTS mode is hardware accelerated for 256 and 107 As of z990 the ECB and CBC mode are hardware accelerated. 108 As of z196 the CTR mode is hardware accelerated.
|
/linux/drivers/video/fbdev/core/ |
H A D | Kconfig | 50 (accelerated) version. 57 This is used by drivers that don't provide their own (accelerated) 66 (accelerated) version. 82 (accelerated) version and the framebuffer is in system RAM. 89 This is used by drivers that don't provide their own (accelerated) 98 (accelerated) version and the framebuffer is in system RAM.
|
/linux/lib/crypto/ |
H A D | Kconfig | 32 accelerated implementation of the Blake2s library interface, 48 accelerated implementation of the ChaCha library interface, 74 accelerated implementation of the Curve25519 library interface, 110 accelerated implementation of the Poly1305 library interface,
|
/linux/Documentation/networking/ |
H A D | failover.rst | 16 This enables paravirtual drivers to use a VF as an accelerated low latency
|
H A D | net_failover.rst | 28 virtio-net accelerated datapath: STANDBY mode 31 net_failover enables hypervisor controlled accelerated datapath to virtio-net
|
H A D | gtp.rst | 71 data plane is accelerated inside the kernel. 74 kernel accelerated path, while the GTP Control Plane goes to
|
/linux/Documentation/fb/ |
H A 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.
|
H A 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 413 + secondary head is not accelerated. There were bad problems with accelerated 433 + secondary head is not accelerated.
|
H A D | lxfb.rst | 37 XF68_FBDev should generally work fine, but it is non-accelerated.
|
H A D | gxfb.rst | 36 XF68_FBDev should generally work fine, but it is non-accelerated.
|
H A D | aty128fb.rst | 42 XF68_FBDev should generally work fine, but it is non-accelerated. As of
|
H A D | tridentfb.rst | 15 All families are accelerated. Only PCI/AGP based cards are supported,
|
/linux/drivers/infiniband/hw/irdma/ |
H A D | trace_cm.h | 229 __entry->accel = cm_node->accelerated; 304 __entry->accel = cm_node->accelerated; 425 __entry->accel = cm_node->accelerated;
|
H A D | cm.h | 325 bool accelerated:1; member
|
H A D | cm.c | 172 cm_node, cm_id, cm_node->accelerated, cm_node->state, type, in irdma_send_cm_event() 196 if (!cm_node->accelerated) in irdma_send_cm_event() 607 cm_node->accelerated, cm_node->state, cm_node->rem_port, in irdma_send_reset() 1857 !cm_node->accelerated && in irdma_reset_list_prep() 2372 if (!cm_node->accelerated && cm_node->accept_pend) { in irdma_destroy_connection() 3762 cm_node->accelerated = true; in irdma_accept() 4178 cm_node->accelerated = true; in irdma_cm_event_connected()
|
/linux/Documentation/devicetree/bindings/leds/ |
H A D | leds-spi-byte.txt | 13 accelerated blinking) might can be supported too.
|
/linux/drivers/net/ethernet/sfc/siena/ |
H A D | Kconfig | 35 features, allowing accelerated network performance in
|
/linux/drivers/video/fbdev/omap/ |
H A D | Kconfig | 49 memory, or don't use any of the accelerated features.
|
/linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
H A D | kconfig.rst | 45 | Requires CONFIG_MLX5_CORE_EN to provide an accelerated interface for the rdma 61 | Enables Hardware-accelerated receive flow steering (arfs) support, and ntuple filtering.
|
H A D | counters.rst | 98 Counters which count traffic that was accelerated by Mellanox driver or by 127 These counters provide information on the amount of traffic that was accelerated 128 by the NIC. The counters are counting the accelerated traffic in addition to the 129 standard counters which counts it (i.e. accelerated traffic is counted twice). 191 - Number of received packets processed using hardware-accelerated GRO. The 197 - Number of received bytes processed using hardware-accelerated GRO. The 203 - The number of GRO SKBs constructed from hardware-accelerated GRO. Only SKBs 208 - Number of receive packets using hardware-accelerated GRO that have large
|
/linux/drivers/net/ethernet/sfc/ |
H A D | Kconfig | 57 features, allowing accelerated network performance in
|
/linux/drivers/net/ethernet/mellanox/mlx5/core/ |
H A D | Kconfig | 39 bool "Mellanox MLX5 ethernet accelerated receive flow steering (ARFS) support" 43 Mellanox MLX5 ethernet hardware-accelerated receive flow steering support,
|
/linux/Documentation/scsi/ |
H A D | cxgb3i.rst | 87 4. To direct open-iscsi traffic to go through cxgb3i's accelerated path,
|
/linux/net/ipv6/ |
H A D | Kconfig | 61 them in the crypto API. You should also enable accelerated 76 them in the crypto API. You should also enable accelerated
|
/linux/drivers/soc/tegra/ |
H A D | Kconfig | 88 and providing 256 CUDA cores. It supports hardware-accelerated en-
|