Lines Matching refs:not

40 *   ``--file-prefix:`` to allow processes that do not want to co-operate to have different memory r…
123 This is less of a problem on Linux, as by default, applications will not
158     help getting more consistent mappings, but not necessarily more reliable -
168     It is not possible to have a primary and secondary instance, or two secondary instances,
172 *   The delivery of interrupts, such as Ethernet* device link status interrupts, do not work in sec…
177 … pointers between multiple processes running based of different compiled binaries is not supported,
187     it may not be possible to have HPET timers available in each DPDK instance.
197 DPDK, there is also a native DPDK IPC API available. It is not intended to be
209 secondary to secondary is not supported.
217 A "message" type does not expect a response and is meant to be a best-effort
224 that are not part of EAL lcore threads.
237 called to ensure that callback will not be triggered again.
254 a value indicating whether sending the message succeeded or not.
285     When an asynchronous request times out, the callback will be called not by
287     this, it may not be possible for DPDK to trigger another interrupt-based
313     Simply returning a value when processing a request callback will not send a
323 requests (i.e. sending a request while responding to another request) is not
324 supported. However, since sending messages (not requests) does not involve an
329 not be mixed: it is not safe to use IPC inside a memory-related callback, nor is
336 inside asynchronous IPC request callbacks. This limitation does not apply to
344 ``rte_mp_reply`` descriptor will not have matching values. This is not treated
351 the callback has not been registered yet. However, once the callback has been