This project is mirrored from git://dpdk.org/next/dpdk-next-virtio.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
- Apr 07, 2022
-
-
Maxime Coquelin authored
Signed-off-by:Maxime Coquelin <maxime.coquelin@redhat.com>
-
- Mar 17, 2022
-
-
Thomas Monjalon authoredSigned-off-by:
Thomas Monjalon <thomas@monjalon.net>
-
- Mar 16, 2022
-
-
Fix grammar, spelling and formatting of DPDK 22.03 release notes. Signed-off-by:John McNamara <john.mcnamara@intel.com>
-
An errata exists where users may see reduced power savings when using PMD Power Management. This issue occurs when compiling DPDK applications with GCC-9 on platforms with TSX enabled. In rte_power_monitor_multi(), the function may return without successfully starting the RTM transaction (the _xbegin() fails). Signed-off-by:David Hunt <david.hunt@intel.com>
-
Compile failed with cflag optimization=1 on Ubuntu20.04 with GCC10.3, it reported vendor_id and dev_id may be used uninitialized in function ifpga_rawdev_fill_info(). Actually it's not the truth, the variables are initialized in function ifpga_get_dev_vendor_id(). To avoid such compile error, the variables are initialized when they are defined. Fixes: 9c006c45 ("raw/ifpga: scan PCIe BDF device tree") Cc: stable@dpdk.org Signed-off-by:
Wei Huang <wei.huang@intel.com> Acked-by:
Tianfei Zhang <tianfei.zhang@intel.com> Acked-by:
Rosen Xu <rosen.xu@intel.com>
-
Blank line added to the final telemetry example for the cryptography device library as to fix the example rendering. Fixes: 1c559ee8 ("cryptodev: add telemetry endpoint for capabilities") Cc: stable@dpdk.org Signed-off-by:
Sean Morrissey <sean.morrissey@intel.com> Acked-by:
Ciara Power <ciara.power@intel.com>
-
The docs mention modifications and additions to the cross file, but there is no demonstration of how those should look like. Signed-off-by:
Juraj Linkeš <juraj.linkes@pantheon.tech> Acked-by:
Ruifeng Wang <ruifeng.wang@arm.com>
-
Numactl cross compilation doesn't work with clang, remove it and fix the GCC cross compiler executable name. Signed-off-by:
-
The newer versions have an extra -none- in the name. Signed-off-by:
-
Remove CFLAGS and LDFLAGS since Meson doesn't support them well enough. Add Meson alternatives: -Dc_args and -Dc_link_args on the command line and in cross files. Signed-off-by:
-
From Documentation/admin-guide/kernel-parameters.txt, specifically the last sentence: nohz_full= [KNL,BOOT,SMP,ISOL] The argument is a cpu list, as described above. In kernels built with CONFIG_NO_HZ_FULL=y, set the specified list of CPUs whose tick will be stopped whenever possible. The boot CPU will be forced outside the range to maintain the timekeeping. Any CPUs in this list will have their RCU callbacks offloaded, just as if they had also been called out in the rcu_nocbs= boot parameter. The kernel or-s the nohz_full cpumask into the rcu_nocbs cpumask at startup, and uses that. Signed-off-by:Tudor Brindus <me@tbrindus.ca>
-
The document roadmap section was missing any mention of the individual drivers guides which are important for users. Add them to list. Signed-off-by:Bruce Richardson <bruce.richardson@intel.com>
-
The document roadmap section called out the titles of other documents, but these are better as hyperlinks. Signed-off-by: -
The document roadmap section was missing any mention of the individual drivers guides which are important for users. Add them to list. Signed-off-by: -
The document roadmap section called out the titles of other documents, but these are better as hyperlinks. Signed-off-by: -
There are two warnings in the VFIO section about limitations of VFIO and limitations on who can bind/unbind devices. Since these don't actually describe any unsafe conditions, and are more informational, we can change these to notes. This also helps emphasise the other warnings in the documents which flag genuine security concerns. Signed-off-by: -
Rather than having separate sections for VFIO and VFIO no-iommu mode, as well as a separate section further down the document on troubleshooting VFIO, we can consolidate all these as subsections into a primary VFIO section. This section starts with the basics of VFIO use, then covers no-iommu mode, before moving on to the more advanced topics such as creating VFs and ending with the troubleshooting subsection. Signed-off-by: -
To further de-emphasise UIO over the alternatives, we can move the UIO section of the drivers page to the end of the document, giving more prominence to VFIO and bifurcated drivers. Signed-off-by: -
The VFIO section of the page about Linux drivers was rather long and unstructured. This can be improved by splitting it up into subsections, to cover the specifics of memory limits and creating VFs. When moving the various text notes into the relevant subsections, we can drop the note about kernels earlier than 3.6, since DPDK no longer supports kernels that old. Signed-off-by: -
VFIO is to be strongly preferred over UIO-based modules, so update our text and examples to only refer to VFIO, giving an initial reference at the start to UIO as a fallback option. Signed-off-by: -
While the details of VFIO and UIO may be of interest to some, most users of the doc are likely primarily interested in how to bind their devices to the kernel driver and then move on to running the app. Therefore, the most important part of the "Linux Drivers" section of the GSG is the subsection on "Binding and Unbinding", so put that first. Signed-off-by: -
The GSG has a note warning that use of UIO is inherently unsafe due to lack of IOMMU protection. However, this was only flagged as a "NOTE", meaning it could easily be missed. Changing the rst tag from "note" to "warning" and moving it to the top of the UIO subsection makes this a lot more visible to users. Signed-off-by: -
The docs on binding drivers was updated as part of the removal of the igb_uio module from the main DPDK repo. As part of that update, a note about uio_pci_generic requiring legacy interrupts was removed, but should have been kept. Fixes: 56bb5841 ("kernel/linux: remove igb_uio") Cc: stable@dpdk.org Signed-off-by:
-
Some IDEs, such as eclipse, complained on save about the use of special characters in the (R) symbol in linux GSG doc. We can replace those with the equivalent "|reg|" text, and including isonum.txt. Cc: stable@dpdk.org Signed-off-by:
-
- Mar 15, 2022
-
-
The "Linux Drivers" section of the GSG already notes that, for use of UIO, the IOMMU must be disabled or put into pass-through mode. Therefore, there is no need to duplicate this information in the "additional functionality" section. Also the kernel configuration options documented in the section are enabled as standard on all common distro kernels, so the information should not be needed in a GSG doc. Signed-off-by: -
The KNI library is disabled by default in DPDK and is already documented in the programmers guide and also in the sample application guide. There are also in-kernel alternatives to it. Therefore, we can drop the (already fairly minimal) reference to it from the Linux GSG. Signed-off-by: -
As best we can tell, the HPET timers are not commonly used, so there is little need to give extensive detail and commentry on them in the Linux GSG. As such, we can reduce the GSG section to just a single subsection and also move it down the page below items which are likely of greater importance. Signed-off-by: -
Not all directories were given in the GSG document, but many of those omitted would be of interest to users, e.g. "doc", "license" and "usertools" directories. Adding these leaves only "devtools", and "kernel" as the only undocumented directories, so add them in too for completeness. When updating the section, add "including" to the line leading up to the directory list, indicating that, while the list is currently complete, it is not guaranteed to always be. Signed-off-by: -
When building end-applications linked with DPDK, the only additional tool needed is pkg-config/pkgconf. However, the standard development tools meta-packages on most distro's include this as standard, meaning it does not really require its own section. The one outlier in the existing text is "alpine" where it is not present when using "libc-dev" target. However, changing "gcc" and "libc-dev" to "alpine-sdk" metapackage aligns alpine with the other distros in this regard. Signed-off-by: -
A note about secure boot not allowing UIO is present in both the system requirements section and the driver binding section. This fits better in the driver binding section, so the copy in system requirements can be removed. The document in general now also emphasises VFIO over UIO more than when this note was first added, reducing the need for this warning to be repeated. Signed-off-by: -
The chipsets referenced in the note[1] were all launched in 2012 and are now discontinued, so we can drop the note about them at this stage. [1] https://ark.intel.com/content/www/us/en/ark/products/codename/44946/products-formerly-cave-creek.html Signed-off-by:
-
Some minor updates for the section on builing DPDK in the GSG: * update Python 3.7 package name to the 3.8 version * note that the pyelftools needs to be tied to the python version * drop reference to jansson library for legacy telemetry * replace special characters for (R) Signed-off-by: -
Add tested platforms with Mellanox NICs to the 22.03 release notes. Signed-off-by:Raslan Darawsheh <rasland@nvidia.com>
-
- Mar 13, 2022
-
-
Lingli Chen authored
Add tested Intel platforms with Intel NICs to v22.03 release note. Signed-off-by:
Lingli Chen <linglix.chen@intel.com> Acked-by:
Xueqin Lin <xueqin.lin@intel.com>
-
- Mar 10, 2022
-
-
Rakesh Kudurumalla authored
Fix the following build error seen with --optimization=1 and GCC 10.3.0. drivers/net/cnxk/cnxk_ethdev_mtr.c: In function ‘cnxk_nix_mtr_policy_validate’: lib/ethdev/rte_mtr_driver.h:188:10: error: ‘str’ may be used uninitialized in this function [-Werror=maybe-uninitialized] drivers/net/cnxk/cn10k_rx.h:149:2 error: ‘frag_ptr’ may be used uninitialized in this function Bugzilla ID: 939 Fixes: b5265990 ("net/cnxk: fix build with GCC 12") Cc: stable@dpdk.org Reported-by:
Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by:
Rakesh Kudurumalla <rkudurumalla@marvell.com> Tested-by:
Daxue Gao <daxuex.gao@intel.com> Acked-by:
Jerin Jacob <jerinj@marvell.com>
-
- Mar 14, 2022
-
-
Thinh Tran authored
The default CPU socket ID was used while creating the Rx queue and this caused creation failure in case if hardware was not resided on the default socket. The patch sets the correct CPU socket ID for the mlx5_rxq_ctrl before calling the mlx5_rxq_create_devx_rq_resources() which eventually calls mlx5_devx_rq_create() with correct CPU socket ID. Fixes: bc5bee02 ("net/mlx5: create drop queue using DevX") Cc: stable@dpdk.org Signed-off-by:
Thinh Tran <thinhtr@linux.vnet.ibm.com> Reviewed-by:
David Christensen <drc@linux.vnet.ibm.com> Acked-by:
Viacheslav Ovsiienko <viacheslavo@nvidia.com> Acked-by:
Matan Azrad <matan@nvidia.com>
-
Jiawei Wang authored
If there are an explicit port match and sample action in the same flow, mlx5 PMD pushes the explicit port match in the prefix subflow, and uses the tag item match in the suffix subflow. The explicit port match was translated into source vport match so the sample suffix subflow lost this match after flow split. This patch copies the explicit port match to the sample suffix subflow, and the latter gets the correct source vport value in the flow matcher. Fixes: b4c0ddbf ("net/mlx5: split sample flow into two sub-flows") Cc: stable@dpdk.org Signed-off-by:
Jiawei Wang <jiaweiw@nvidia.com> Acked-by:
-
- Mar 15, 2022
-
-
Thomas Monjalon authored
Signed-off-by:Thomas Monjalon <thomas@monjalon.net> -
When compiling on FreeBSD with clang and include checking enabled, errors are emitted due to differences in how empty structs/unions are handled in C and C++, as C++ structs cannot have zero size. lib/eventdev/rte_eventdev.h:992:2: error: union has size 0 in C, non-zero size in C++ Since the contents of the union are all themselves of zero size, the actual union wrapper is unnecessary. We therefore remove it for C++ builds - though keep it for C builds for safety and clarity of understanding the code. The alignment constraint on the union is unnecessary in the case where the whole struct is aligned on a 16-byte boundary, so we add that constraint to the overall structure to ensure it applies for C++ code as well as C. Fixes: 1cc44d40 ("eventdev: introduce event vector capability") Cc: stable@dpdk.org Signed-off-by:
-
When compiling on FreeBSD with clang and include checking enabled, errors are emitted due to differences in how empty structs/unions are handled in C and C++, as C++ structs cannot have zero size. lib/cryptodev/rte_crypto.h:127:2: error: union has size 0 in C, non-zero size in C++ Since the contents of the union are all themselves of zero size, the actual union wrapper is unnecessary. We therefore remove it for C++ builds - though keep it for C builds for safety and clarity of understanding the code. Fixes: c0f87eb5 ("cryptodev: change burst API to be crypto op oriented") Fixes: d2a4223c ("cryptodev: do not store pointer to op specific params") Cc: stable@dpdk.org Signed-off-by:
-
