On 24/05/2022 10:38, Bruce Richardson wrote:
On Tue, May 24, 2022 at 10:25:01AM +0100, Kevin Laatz wrote:
During EAL init, all buses are probed and the devices found are
initialized. On eal_cleanup(), the inverse does not happen, meaning any
allocated memory and other configuration will not be
On 24/05/2022 15:48, Stephen Hemminger wrote:
On Tue, 24 May 2022 10:25:01 +0100
Kevin Laatz wrote:
+
+ RTE_LOG(DEBUG, EAL,
+ "Clean up PCI driver: %s (%x:%x) device:
"PCI_PRI_FMT" (socket %i)\n",
+ drv->driver.name, de
On Tue, 24 May 2022 10:25:01 +0100
Kevin Laatz wrote:
> +
> + RTE_LOG(DEBUG, EAL,
> + "Clean up PCI driver: %s (%x:%x) device:
> "PCI_PRI_FMT" (socket %i)\n",
> + drv->driver.name, dev->id.vendor_id,
> dev->id.device_id,
> +
On Tue, May 24, 2022 at 10:25:01AM +0100, Kevin Laatz wrote:
> During EAL init, all buses are probed and the devices found are
> initialized. On eal_cleanup(), the inverse does not happen, meaning any
> allocated memory and other configuration will not be cleaned up
> appropriately on exit.
>
> Cu
During EAL init, all buses are probed and the devices found are
initialized. On eal_cleanup(), the inverse does not happen, meaning any
allocated memory and other configuration will not be cleaned up
appropriately on exit.
Currently, in order for device cleanup to take place, applications must
cal
5 matches
Mail list logo