| /dpdk/lib/cmdline/ |
| H A D | cmdline.c | 140 int i, same; in cmdline_in() local
153 same = !memcmp(buffer, history, histlen) && in cmdline_in()
157 same = 0; in cmdline_in()
159 if (buflen > 1 && !same) in cmdline_in()
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | lpm_lib.rst | 25 …If there is no rule with the same prefix present in the table, then the new rule is added to the L…
26 …If a rule with the same prefix is already present in the table, the next hop of the rule is update…
34 … In the case that there are multiple rules present in the LPM table that have the same 32-bit key,
62 which would be the same as having a single table with 2^32 entries.
100 Next hop and depth contain the same information as in the tbl24.
140 Hence, in this case, we copy the exact same entry to every position indexed by one of these combina…
154 If a replacement rule is found, target tbl24 and tbl8 entries are updated to have the same depth an…
161 After deleting a rule, a group of tbl8s that belongs to the same tbl24 entry are freed in following…
165 * All tbl8s in the group have the same values and with depth no greater than 24.
210 and the first 24 bits of this rule are not the same as the first 24 bits of a rule previously added.
[all …]
|
| H A D | packet_distrib_lib.rst | 41 This ensures that no two packets with the same tag are processed in parallel,
42 and that all packets with the same tag are processed in input order.
59 Within this set of returned packets, all packets sharing the same tag will be returned in their ori…
65 therefore that additional packets with the same tag can safely be distributed to other workers --
|
| H A D | multi_proc_support.rst | 30 Secondary processes should run alongside primary process with same DPDK version.
33 be passed with the same allow and block options.
57 When a secondary process is started, these files are read and the EAL recreates the same memory con…
59 and point to the same objects, in both processes.
68 same switch specified. Otherwise, memory corruption may occur.
86 …upport can be used to create a set of peer processes where each process performs the same workload.
87 This model is equivalent to having multiple threads each running the same main-loop function,
139 In the same way that it is possible to run independent DPDK applications side- by-side on a single …
141 In this case, the secondary processes must use the same ``--file-prefix`` parameter
155 * The multi-process feature requires that the exact same hugepage memory mappings be present in a…
[all …]
|
| H A D | ring_lib.rst | 78 It is not possible to create two rings with the same name (rte_ring_create() returns NULL if this i…
107 The initial state is to have a prod_head and prod_tail pointing at the same location.
128 The second step is to modify *ring->prod_head* in ring structure to point to the same location as p…
143 …e ring, ring->prod_tail in the ring structure is modified to point to the same location as *ring->…
160 The initial state is to have a cons_head and cons_tail pointing at the same location.
181 The second step is to modify ring->cons_head in the ring structure to point to the same location as…
196 Finally, ring->cons_tail in the ring structure is modified to point to the same location as ring->c…
213 The initial state is to have a prod_head and prod_tail pointing at the same location.
235 The second step is to modify ring->prod_head in the ring structure to point to the same location as…
|
| H A D | lpm6_lib.rst | 35 …If there is no rule with the same prefix present in the table, then the new rule is added to the L…
36 …If a rule with the same prefix is already present in the table, the next hop of the rule is update…
44 …In the case that there are multiple rules present in the LPM table that have the same 128-bit valu…
61 whether there are other rules with bigger depths and the same key in the data structure.
108 Both types of tables share the same structure.
152 Hence, in this case, we copy the exact same entry to every position indexed by one of these combina…
197 If they share the same first 24 bits, for instance, the tbl8 at the second level will be shared.
199 two 48 bit-long rules may use the same three tbl8s if the only difference is in their last byte.
|
| H A D | regexdev.rst | 15 The RegEx library follows the same basic principles as those used in DPDK's
145 Multiple logical cores should never share the same queue pair for enqueuing
146 operations or dequeuing operations on the same RegEx device since this would
172 The dequeue API uses the same format as the enqueue API of processed but
|
| H A D | qos_framework.rst | 97 while several other blocks could be mapped to the same CPU core.
136 Each queue hosts packets from one or multiple connections of the same type belonging to the same us…
344 …al ports on different threads. The enqueue and dequeue of the same port are run by the same thread.
346 #. Splitting the same physical port to different threads by running different sets of subports of …
348 The enqueue and dequeue of the same port are run by the same thread.
379 keeps the scheduler data structures internal to the same core.
932 allocated for the same traffic class at the parent subport level.
1194 different RED configurations for the same packet queue at run-time.
1589 for each packet color (green, yellow, red) in the same traffic class (tc).
1730 with the two buckets sharing the same token update rate:
[all …]
|
| H A D | poll_mode_drv.rst | 61 In the same way, every receive queue of a port is assigned to and polled by a single logical core (…
264 Then the same packet can be transmitted to the next destination interface.
287 lockfree multithreaded TX burst on the same TX queue.
301 * A per-queue offloading can be enabled on a queue and disabled on another queue at the same time.
303 * A pure per-port offloading can't be enabled on a queue and disabled on another queue at the same …
304 * A pure per-port offloading must be enabled or disabled on all queues at the same time.
305 * Any offloading is per-queue or pure per-port type, but can't be both types at same devices.
338 not to be invoked in parallel on different logical cores to work on the same target object.
339 …tion cannot be invoked in parallel on two logical cores to poll the same RX queue of the same port.
404 driver-specific, and hence might not be the same for different ports.
[all …]
|
| H A D | hash_lib.rst | 12 For increased performance the DPDK Hash requires that all the keys have the same number of bytes wh…
144 …rison is still necessary, as two input keys from the same bucket can still potentially have the sa…
152 If signature is not in the primary bucket, the secondary bucket is looked up, where same procedure
164 is stored in it. If not, same process is repeated (one of the entries gets pushed) until an empty e…
184 …FLAGS_EXT_TABLE flag is set, the hash table implementation still uses the same Cuckoo Hash algorit…
193 The deletion is the same as the case when the RTE_HASH_EXTRA_FLAGS_EXT_TABLE flag is not set. With …
266 so the same set of operations is applied to all the packets from the same flow.
277 …emented as an array, the application should create a hash object with the same number of entries a…
|
| H A D | packet_framework.rst | 288 Several keys can share the same signature (collisions).
458 The same CPU core reads the key from the packet meta-data, uses it to compute the key signature
506 when the next pipeline stage eventually gets executed for the same packets,
521 before same packets 0 and 1 are used (i.e. before stage 1 is executed on packets 0 and 1),
979 …* A table can have multiple entries (including the default entry) connected to the same output p…
981 …Different tables can have entries (including default table entry) connected to the same output por…
984 in which case all these entries have to point to the same table.
1049 Within the same table, all the table entries (including the table default entry) share the same def…
1096 and actions that can be fitted on the same CPU core due to HW constraints like:
1108 It is allowed for the same core to run several pipelines, but it is not allowed for several cores t…
[all …]
|
| H A D | toeplitz_hash_lib.rst | 38 to be exactly the same as the one installed on the NIC.
78 in this case it would be useful to find another tuple whose hash has the same
185 same as in ``desired_hash``.
227 That leads to a situation where the same packet flow can be shared between two
243 belonging to one bidirectional flow will be assigned to the same queue, as
274 * way that the reverse tuple will have the same LSBs as the original
|
| H A D | generic_receive_offload_lib.rst | 77 safe. So if different processes or threads want to access the same
115 searches for a matched "flow" (i.e., the same value of key) for the
123 Packets in the same "flow" that can't merge are always caused
203 packet_type to the same values as the protocol headers of the
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | qos_scheduler.rst | 144 The same information is shown in bytes.
149 The same information is shown in bytes.
154 All of these commands work the same way, averaging the number of packets throughout a specific subs…
188 Another example with 2 packet flow configurations using different ports but sharing the same core f…
211 * A queue hosts packets from one or multiple connections of the same type belonging to the same u…
233 …| Traffic Class | 13 | TCs of the same pipe services in strict priority | De…
|
| H A D | dist_app.rst | 139 Command line parsing is done in the same way as it is done in the L2 Forwarding Sample
142 Mbuf pool initialization is done in the same way as it is done in the L2 Forwarding
145 Driver Initialization is done in same way as it is done in the L2 Forwarding Sample
148 RX queue initialization is done in the same way as it is done in the L2 Forwarding
151 TX queue initialization is done in the same way as it is done in the L2 Forwarding
|
| H A D | link_status_intr.rst | 73 Command line parsing is done in the same way as it is done in the L2 Forwarding Sample Application.
79 Mbuf pool initialization is done in the same way as it is done in the L2 Forwarding Sample Applicat…
240 For this test application, the processing is exactly the same for all packets arriving on the same …
242 to send all the received packets on the same TX port using
246 packet N is not necessarily forwarded on the same port as packet N-1.
247 The application is implemented to illustrate that so the same approach can be reused in a more comp…
|
| H A D | multi_process.rst | 16 The multi-process example applications are built in the same way as other sample applications,
76 again run the same binary setting at least two cores in the coremask/corelist:
136 with each process performing the same set of packet- processing operations.
172 and the first two must be the same as those passed to the primary instance, or errors result.
193 For the symmetric multi-process example, since all processes work in the same manner,
204 The initialization calls in both the primary and secondary instances are the same for the most part,
228 is exactly the same - each process reads from each port using the queue corresponding to its proc-i…
293 In the same way that the server process is designed to be run as a primary process instance only,
|
| /dpdk/examples/pipeline/examples/ |
| H A D | fib.spec | 6 ; to co-exist as part of the same "physical" routing table; the VRF ID typically identifies the
15 ; typical 3-tuple) by always selecting the same next hop for packets that are part of the same flow.
|
| /dpdk/doc/guides/nics/ |
| H A D | memif.rst | 19 at same time. The peer interface is identified by id parameter. Server
33 interfaces using same socket, be sure to specify unique ids ``id=0``, ``id=1``,
35 listener socket. Listener socket can not be used by a client interface on same
56 process. Each interface can be connected to one interface at same time,
65 at the same time, provided each role is assigned unique socket.
189 Server interface functions the same as with zero-copy disabled.
282 To set the loopback, just use the same socket and id with different roles::
|
| H A D | nfp.rst | 69 have a PMD able to work with the PF and VFs at the same time and with the PF
98 more than one SmartNIC, same type of SmartNIC or different ones, and to upload a
109 The NFP PMD can work with up to 8 ports on the same PF device. The number of
119 NFP ports belonging to same PF can be seen inside PMD initialization with a
152 same time because the VFs require the PF being bound to the NFP PF Linux
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | sw.rst | 11 cores to multiplex other work on the same core if required.
126 Parallel traffic to the same queue, but scheduling each of them appropriately.
129 same queue is that it causes excessive branching in the code to enqueue packets
|
| /dpdk/doc/guides/tools/ |
| H A D | pdump.rst | 99 should both be passed with the same file name or the same Linux iface name.
106 … of the mbuf data. This is used internally for mempool creation. Ideally this value must be same as
|
| H A D | proc_info.rst | 75 * dpdk-procinfo should run alongside primary process with same DPDK version.
78 pass the same NIC PMD libraries as used for the primary application. Any
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | scheduler.rst | 17 a software crypto PMD and shares the same API provided by librte_cryptodev.
133 parameter to achieve the same purpose. For example:
155 round-robin manner. If scheduler cannot enqueue entire burst to the same worker,
163 are supported. Only the same type of cryptodevs should be used concurrently.
|
| /dpdk/drivers/net/ |
| H A D | meson.build | 65 std_deps += ['bus_vdev'] # same with vdev bus
|