| /dpdk/examples/ipsec-secgw/test/ |
| H A D | tun_3descbc_sha1_common_defs.sh | 33 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
35 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
40 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
42 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
48 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
50 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
55 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
101 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
108 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
116 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
[all …]
|
| H A D | tun_aesctr_sha1_common_defs.sh | 32 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
34 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
38 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
40 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
45 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
47 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
51 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
53 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
98 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
104 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
[all …]
|
| H A D | tun_aescbc_sha1_common_defs.sh | 32 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
34 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
38 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
40 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
45 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
47 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
53 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
98 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
104 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
111 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
[all …]
|
| H A D | trs_3descbc_sha1_common_defs.sh | 33 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
35 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
40 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
42 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
48 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
50 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
56 de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
58 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
|
| H A D | trs_aesctr_sha1_common_defs.sh | 32 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
34 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
38 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
40 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
45 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
47 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
52 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
54 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
|
| H A D | trs_aescbc_sha1_common_defs.sh | 32 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
34 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
38 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
40 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
45 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
47 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
52 cipher_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
54 auth_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
|
| H A D | tun_aesgcm_common_defs.sh | 32 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
36 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
41 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
45 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
88 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
92 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
97 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
101 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
|
| H A D | trs_aesgcm_common_defs.sh | 32 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
36 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
41 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
45 aead_key de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef:de:ad:be:ef \
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 66 The OCTEON TX crypto poll mode driver can be compiled either natively on
74 OCTEON TX crypto PF driver needs microcode to be available at `/lib/firmware/` directory.
82 The number of crypto VFs to be enabled can be controlled by setting sysfs entry,
89 The device bus ID, `dev_bus_id`, to be used in the above step can be found out
90 by using dpdk-devbind.py script. The OCTEON TX crypto PF device need to be
91 identified and the corresponding device number can be used to tune various PF
95 Once the required VFs are enabled, dpdk-devbind.py script can be used to
96 identify the VFs. To be accessible from DPDK, VFs need to be bound to vfio-pci
105 Appropriate huge page need to be setup in order to run the DPDK example
112 Example applications can now be executed with crypto operations offloaded to
[all …]
|
| H A D | scheduler.rst | 46 The following parameters (all optional) can be provided in the previous
50 to be allocated (by default, socket_id will be the socket where the core
53 * max_nb_sessions: Specify the maximum number of sessions that can be
54 created. This value may be overwritten internally if there are too
59 here. Multiple cryptodevs can be attached initially by presenting this
87 the scheduler first, otherwise an error will be returned.
90 every mbuf to be processed to store temporary data. By the end of
92 stored value of this field will be lost.
146 operations fail to be enqueued, then they will be enqueued to the secondary
169 These cores should be present in EAL core list parameter and
[all …]
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | deprecation.rst | 8 <../contributing/abi_policy>`. API and ABI deprecation notices are to be posted
24 operations must be used for patches that need to be merged in 20.08 onwards.
32 ``__atomic_thread_fence`` must be used for patches that need to be merged in
36 be removed in DPDK 22.11. The replacement macro
40 deprecated and will be removed in DPDK 22.11. Use replacement macro
44 will be removed in DPDK 22.11.
67 will be removed in DPDK 20.11.
86 will be limited to maximum 256 queues.
98 any PMD, so they will be removed in DPDK 22.11.
106 The legacy actions should be deprecated in 22.07, once MODIFY_FIELD
[all …]
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | ioat.rst | 21 be done by software, freeing up CPU cycles for other tasks.
27 can be used to show the presence of supported hardware.
45 if the raw drivers are to be used instead::
53 or be bound to a user-space IO driver for use.
65 An example of how this may be done can be seen in the script ``dpdk_idxd_cfg.py``
72 such as priority or queue depth, need to be set for each queue.
95 Once the devices have been configured, they need to be enabled::
107 The HW devices to be used will need to be bound to a user-space IO driver for use.
173 be NULL, or else be set to point to a structure of type
175 input ring will be returned in that structure.
[all …]
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | l2_forward_crypto.rst | 87 * cipher_key: set the ciphering key to be used. Bytes has to be separated with ":"
91 which will be generated randomly.
95 * cipher_iv: set the cipher IV to be used. Bytes has to be separated with ":"
107 * auth_key: set the authentication key to be used. Bytes has to be separated with ":"
111 which will be generated randomly.
115 * auth_iv: set the auth IV to be used. Bytes has to be separated with ":"
127 * aead_key: set the AEAD key to be used. Bytes has to be separated with ":"
135 * aead_iv: set the AEAD IV to be used. Bytes has to be separated with ":"
141 * aad: set the AAD to be used. Bytes has to be separated with ":"
232 the latter will be ignored.
[all …]
|
| /dpdk/doc/guides/contributing/ |
| H A D | documentation.rst | 145 It can be installed as follows:
339 * Inline text that is required to be rendered with a fixed width font should be enclosed in backquo…
349 highlighting can be applied.
358 That can be applied as follows::
371 Which would be rendered as:
396 This would be rendered as:
419 This can be done as follows:
453 * Long lines that cannot be wrapped, such as application output, should be truncated to be less tha…
463 These will be converted to SVG in time.
509 * RST tables should be used sparingly.
[all …]
|
| H A D | coding_style.rst | 25 [Tab stop size should be assumed to be 8-characters wide].
38 These comments should be used in normal cases.
499 * Parts of a for loop may be left empty.
546 Exits should be 0 on success, or 1 on failure.
591 * Functions local to one source module should be declared static, and should not be prototyped unle…
753 * Functions that should be inlined should to be declared as ``static inline`` and can be defined in…
851 All Python code should be compliant with
906 A simple example of use would be:
982 it does not need to be specified here.
990 never be needed for new libraries.
[all …]
|
| H A D | stable.rst | 32 Any release of DPDK can be designated as a Stable Release if a
35 If a version is to be a "Stable Release", it should be designated as such
54 A stable release can be designated as an LTS release based on community
58 After the X.11 release, an LTS branch will be created for it at
59 https://git.dpdk.org/dpdk-stable where bugfixes will be backported to.
79 What changes should be backported
85 they will be discussed on the mailing lists.
104 New features should not be backported to stable releases.
123 Performance improvements are generally not considered to be fixes,
124 but may be considered in some cases where:
[all …]
|
| /dpdk/doc/guides/dmadevs/ |
| H A D | idxd.rst | 12 This PMD can be used in conjunction with Intel\ |reg| DSA devices to offload
19 The ``dpdk-devbind.py`` script, included with DPDK, can be used to show the
29 For builds using ``meson`` and ``ninja``, the driver will be built when the
46 An example of how this may be done can be seen in the script ``dpdk_idxd_cfg.py``
52 need to be assigned to groups, and the various other configuration options,
53 such as priority or queue depth, need to be set for each queue.
75 Once the devices have been configured, they need to be enabled::
113 The HW devices to be used will need to be bound to a user-space IO driver for use.
146 are also available to further restrict the device list that will be used.
162 To use the devices from an application, the dmadev API can be used.
[all …]
|
| H A D | ioat.rst | 14 cloning packet data, to be accelerated by IOAT hardware rather than having to
15 be done by software, freeing up CPU cycles for other tasks.
20 The ``dpdk-devbind.py`` script, included with DPDK, can be used to show the
23 list. For Intel\ |reg| IOAT devices, the hardware will often be listed as
35 For builds using ``meson`` and ``ninja``, the driver will be built when the
42 user-space IO driver such as ``vfio-pci`` in order to be used by DPDK.
57 devices will be found as part of the device scan done at application
61 be used in the same way that other DPDK devices use them.
68 "DMA device type" inside DPDK, and can be accessed using APIs from the
74 To use IOAT devices from an application, the ``dmadev`` API can be used.
[all …]
|
| /dpdk/doc/guides/freebsd_gsg/ |
| H A D | build_dpdk.rst | 26 These can be installed using (as root)::
32 need to be installed. If not already present on the system, these can be
45 The final, install, step generally needs to be run as root::
61 It is recommended that pkg-config be used to query information
80 system, the module can be found in the `/boot/modules` directory.
83 contiguous blocks to be reserved by the module can be set at runtime prior to
97 The variables can be inspected using the following command::
105 The module can then be loaded using kldload::
124 are not to be used.
132 available and can be verified via dmesg or ``/var/log/messages``::
[all …]
|
| /dpdk/doc/guides/nics/ |
| H A D | cnxk.rst | 11 More information can be found at `Marvell Official Website
138 RTE flow entries can be pre allocated and the size of pre allocation can be
182 Info format will be "offset/mask/shift direction". All parameters has to be
183 in hexadecimal format and mask should be contiguous. Info can be configured
192 mask 0x7e and right shift will be used to get the size. That is, size will be
268 later original SPI value can be updated using session update.
309 This behaviour can be changed to pick mode ``2`` by using
341 will be used when creating flow rules on the SDP device.
399 * ``vlan_exdsa`` and ``exdsa`` can be parsed at L2 level.
400 * ``NGIO`` can be parsed at L3 level.
[all …]
|
| /dpdk/doc/guides/platform/ |
| H A D | octeontx.rst | 12 More information about SoC can be found at `Cavium, Inc Official Website
50 For example, the *aarch64* Linaro Toolchain, which can be obtained from
55 Any *aarch64* supporting filesystem can be used. For example,
56 Ubuntu 15.10 (Wily) or 16.04 LTS (Xenial) userland which can be obtained
70 The OCTEON TX platform drivers can be compiled either natively on
73 The **OCTEON TX** :sup:`®` board must be running the linux kernel based on
83 native architecture, the linux sources need to be compiled once natively.
93 drivers can be compiled with the following steps,
100 The example applications can be compiled using the following:
133 The example applications can be compiled using the following:
[all …]
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | linux_drivers.rst | 15 and network ports should be bound to that driver.
35 Most devices require that the hardware to be used by DPDK be unbound from the kernel driver it uses,
37 …, any network ports or other hardware under Linux* control will be ignored and cannot be used by t…
48 Note that the UIO or VFIO kernel modules to be used,
54 to which devices can be used with VFIO.
126 both kernel and BIOS must support and be configured
268 could not be enabled because there is no IOMMU support.
320 More about the bifurcated driver can be found in
332 and can only be done by root user.
336 can be used as a substitute for VFIO. This module can be loaded using the command:
[all …]
|
| H A D | sys_reqs.rst | 16 and high performance of small packets, BIOS setting changes may be needed.
94 For poll-mode drivers, the additional dependencies for each driver can be
114 The kernel version in use can be checked using the command::
120 The version can be checked using the ``ldd --version`` command.
151 The reservation of hugepages can be performed at run time.
162 However, pages can also be reserved explicitly on individual NUMA nodes
168 The tool ``dpdk-hugepages.py`` can be used to manage hugepages.
173 so reserving them at boot time may be the only option.
190 can also be optionally set as the default hugepage size for the system.
219 mount points for hugepages need to be created.
[all …]
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | multi_proc_support.rst | 33 be passed with the same allow and block options.
159 if the mappings are wrong, they will be consistently wrong!
198 performance-critical, but rather is intended to be a convenient, general
229 Before any messages can be received, a callback will need to be registered.
237 called to ensure that callback will not be triggered again.
243 of fields to be populated are as follows:
267 This is where the responses will be stored.
268 The list of fields that will be populated by IPC are as follows:
277 memory must be freed by the requestor after request completes!
299 To receive a message, a name callback must be registered using the
[all …]
|
| H A D | metrics_lib.rst | 11 practice producers will typically be other libraries or primary
12 processes, whereas consumers will typically be applications.
31 Before the library can be used, it has to be initialized by calling
48 be done individually, or a set of metrics can be registered as a group.
72 can be obtained using ``rte_metrics_get_names()``.
169 This function **must** be called from a primary process.
187 statistics can be obtained by querying the metrics library.
192 Before the library can be used, it has to be initialised by calling
216 desired, this function should be called once a second.
256 Before the library can be used, it has to be initialised by calling
[all …]
|