On Wed, Feb 05, 2025 at 04:47:20PM +0100, Thomas Monjalon wrote: > 05/02/2025 15:59, Bruce Richardson: > > On Wed, Feb 05, 2025 at 03:43:30PM +0100, Thomas Monjalon wrote: > > > 05/02/2025 15:37, Renyong Wan: > > > > On 2025/2/5 19:44, Thomas Monjalon wrote: > > > > > 28/01/2025 15:46, Renyong Wan: > > > > >> XSC PMD is designed to support both VFIO and private kernel drivers. > > > > > What's the benefit of private kernel drivers? Why are they private? > > > > > > > > Hello Thomas, > > > > > > > > Thanks for your review. > > > > > > > > It can support the bifurcation model without unbinding the kernel > > > > driver, by utilizing our private kernel driver in conjunction with > > > > rdma-core. Currently, our kernel driver is not open-source, so it is > > > > considered a private kernel driver. This patch series only supports the > > > > VFIO driver. Our kernel driver is currently in the process of being > > > > open-sourced on kernel.org, and once it is available there, we also > > > > plan to submit the code that supports our kernel driver to DPDK. > > > > > > OK that's interesting, thank you. > > > > > > I think it would be the first DPDK driver to support both VFIO or > > > bifurcated model. > > > > > > > Not quite the first, but possibly the first net driver? :-). The idxd > > dmadev driver supports both. It can be used either with VFIO or the kernel > > idxd driver. > > It announces only VFIO: > RTE_PMD_REGISTER_KMOD_DEP(IDXD_PMD_DMADEV_NAME_PCI, "vfio-pci"); > > How does it work? > It also has its own bus driver that scans for dev nodes (/dev/dsa/wq*) on probe, and uses those configured for DPDK use. On a system with multiple device instances you can have one device used by DPDK bound to vfio, and use a couple of work queues from another device bound to the idxd kernel driver. More info on the setup is in the docs [1]
/Bruce [1] https://doc.dpdk.org/guides-24.11/dmadevs/idxd.html#device-setup
