Lines Matching refs:not

17 Memory Copy: Do not Use libc in the Data Plane
22 However, many of these functions are not designed for performance.
23 Functions such as memcpy() or strcpy() should not be used in the data plane.
37 but it is really not advised to use malloc-like functions in the data plane because
38 managing a fragmented heap can be costly and the allocator may not be optimized for parallel alloca…
54 *   Use RTE_PER_LCORE variables. Note that in this case, data on lcore X is not available to lcore …
68 it should not be a problem to keep them in one socket only, since data will be present in cache.
151 The packets are not transmitted until the tail pointer is updated on the corresponding TX queue of …
156 However, this is not very desirable when tuning for low latency because
159 the NIC will not know to transmit the packets until the TX tail pointer has been updated,
160 which is not done until all 32 packets have been processed for transmission.
203 does not matter. For example, the packet statistics counters need to be
204 incremented atomically but do not need any particular memory ordering.
215 are not allowed to move above the lock. In this case, the full memory barrier
219 section are not allowed to move below the unlock. So the full barrier in the
245 However, this technique is not always efficient; it depends on many factors including the compiler.
251 allow the developer to indicate if a code branch is likely to be taken or not.
266 If the compiler version does not support the specific feature set (for example, the Intel® AVX inst…
269 Since the build and runtime targets may not be the same,