Lines Matching refs:vector
152 supports the newer vector IO devices which are significantly faster
163 # vector UML network devices
206 | tap | vector | checksum, tso | > 8Gbit |
208 | hybrid | vector | checksum, tso, multipacket rx | > 6GBit |
210 | raw | vector | checksum, tso, multipacket rx, tx" | > 6GBit |
212 | EoGRE | vector | multipacket rx, tx | > 3Gbit |
214 | Eol2tpv3 | vector | multipacket rx, tx | > 3Gbit |
216 | bess | vector | multipacket rx, tx | > 3Gbit |
218 | fd | vector | dependent on fd type | varies |
257 For newer network drivers like the vector transports, ``root`` privilege
262 of running UML as root. In case of vector transport, a user can add the
271 Configuring vector transports
274 All vector transports support a similar syntax:
286 * ``depth=int`` - sets the queue depth for vector IO. This is the
343 While tap relies on the vector infrastructure, it is not a true vector
379 This transport uses vector IO on raw sockets. While you can bind to any
562 more recent versions is using vector IO for high performance.
581 Legacy transports are now considered obsolete. Please use the vector