Lines Matching full:same
30 UMEM. RX and TX can share the same UMEM so that a packet does not have
165 to the same chunk. If the user application is run in the unaligned
261 This flag enables you to bind multiple sockets to the same UMEM. It
262 works on the same queue id, between queue ids and between
269 sockets bound to the same netdev and queue id. The UMEM (tied to the
315 same UMEM. However, note that you need to supply the
324 to two different queue ids on the same netdev. Create the first socket
330 socket. These two sockets will now share one and the same UMEM.
333 case where sockets were bound to the same queue id and
344 one. Both methods yield the same result.
346 Note that a UMEM can be shared between sockets on the same queue id
347 and device, as well as between queues on the same device and between
348 devices at the same time.
388 driver on the same core, but also if you use different cores for the
406 do not try to access them from multiple processes at the same
600 to sockets bound to the same queue id X. The XSKMAP can contain
603 to the same queue id Y. In zero-copy mode, you should use the
609 A: Care has to be taken not to feed the same buffer in the UMEM into
610 more than one ring at the same time. If you for example feed the
611 same buffer into the FILL ring and the TX ring at the same time, the
612 NIC might receive data into the buffer at the same time it is
613 sending it. This will cause some packets to become corrupted. Same
614 thing goes for feeding the same buffer into the FILL rings