Searched refs:accelerated (Results 1 – 25 of 48) sorted by relevance
12
| /linux-6.1.9/arch/s390/crypto/ |
| D | Kconfig | 95 As of z9 the ECB and CBC modes are hardware accelerated
98 As of z10 the ECB and CBC modes are hardware accelerated
101 As of z196 the CTR mode is hardware accelerated for all AES
102 key sizes and XTS mode is hardware accelerated for 256 and
119 As of z990 the ECB and CBC mode are hardware accelerated.
120 As of z196 the CTR mode is hardware accelerated.
|
| /linux-6.1.9/lib/crypto/ |
| D | Kconfig | 18 accelerated implementation of the Blake2s library interface,
34 accelerated implementation of the ChaCha library interface,
60 accelerated implementation of the Curve25519 library interface,
96 accelerated implementation of the Poly1305 library interface,
|
| /linux-6.1.9/Documentation/devicetree/bindings/crypto/ |
| D | intel,keembay-ocs-aes.yaml | 14 hardware-accelerated AES/SM4 encryption/decryption.
|
| D | intel,keembay-ocs-hcu.yaml | 15 provides hardware-accelerated hashing and HMAC.
|
| /linux-6.1.9/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.rst | 71 data plane is accelerated inside the kernel.
74 kernel accelerated path, while the GTP Control Plane goes to
|
| /linux-6.1.9/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 | gxfb.rst | 36 XF68_FBDev should generally work fine, but it is non-accelerated.
|
| D | lxfb.rst | 37 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
413 + secondary head is not accelerated. There were bad problems with accelerated
433 + 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-6.1.9/Documentation/devicetree/bindings/leds/ |
| D | leds-spi-byte.txt | 13 accelerated blinking) might can be supported too.
|
| /linux-6.1.9/drivers/infiniband/hw/irdma/ |
| D | trace_cm.h | 229 __entry->accel = cm_node->accelerated;
304 __entry->accel = cm_node->accelerated;
425 __entry->accel = cm_node->accelerated;
|
| D | cm.h | 325 bool accelerated:1; member
|
| 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()
1809 !cm_node->accelerated && in irdma_reset_list_prep()
2319 if (!cm_node->accelerated && cm_node->accept_pend) { in irdma_destroy_connection()
3708 cm_node->accelerated = true; in irdma_accept()
4114 cm_node->accelerated = true; in irdma_cm_event_connected()
|
| /linux-6.1.9/drivers/net/ethernet/sfc/siena/ |
| D | Kconfig | 35 features, allowing accelerated network performance in
|
| /linux-6.1.9/drivers/video/fbdev/omap/ |
| D | Kconfig | 60 memory, or don't use any of the accelerated features.
|
| /linux-6.1.9/drivers/net/ethernet/sfc/ |
| D | Kconfig | 55 features, allowing accelerated network performance in
|
| /linux-6.1.9/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | Kconfig | 38 bool "Mellanox MLX5 ethernet accelerated receive flow steering (ARFS) support"
42 Mellanox MLX5 ethernet hardware-accelerated receive flow steering support,
|
| /linux-6.1.9/Documentation/scsi/ |
| D | cxgb3i.rst | 87 4. To direct open-iscsi traffic to go through cxgb3i's accelerated path,
|
| /linux-6.1.9/net/ipv6/ |
| 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-6.1.9/drivers/soc/tegra/ |
| D | Kconfig | 88 and providing 256 CUDA cores. It supports hardware-accelerated en-
|
| /linux-6.1.9/drivers/video/fbdev/ |
| D | Kconfig | 45 (e.g. an accelerated X server) and that are not frame buffer
75 (accelerated) version.
82 This is used by drivers that don't provide their own (accelerated)
91 (accelerated) version.
107 (accelerated) version and the framebuffer is in system RAM.
114 This is used by drivers that don't provide their own (accelerated)
123 (accelerated) version and the framebuffer is in system RAM.
1179 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1655 bool "VT8500/WM8xxx accelerated raster ops support"
1658 This adds support for accelerated raster operations on the
|
12