2015-10-21 15:39, Alejandro Lucero:
> On Wed, Oct 21, 2015 at 6:24 AM, David Marchand <david.marchand at 6wind.com>
> wrote:
> > Please, can you elaborate on the need for (yet another) uio driver, rather
> > than make igb_uio work with your hardware ?
[...]
> I have been looking at the possibility of getting rid of nfp_uio. The fact
> is our PMD can work without it, both for the PF and VF (not the PMD version
> already submitted but one under development). The PF support requires not
> using UIO at all, because the device is attached to the BSP driver. The
> only problem with this approach is we do not have support for interrupts,
> what is not critical (I can see other PMDs not having support for Link
> Status Changes) but we do not like it as programs can register callbacks
> for these interrupts which would not work at all.
>
> Interrupt support could be implemented in the BSP, doing the same UIO or
> VFIO do, but this will require (minor) changes to DPDK for having another
> intr_handle (not UIO, not VFIO). I do not know if other PMDs could also
> make use of such a change but I guess that would help to accept those
> changes.
We are going to have an external handler (used for mlx5):
http://dpdk.org/ml/archives/dev/2015-October/024678.html
Problem solved :)
Is it possible to rework your PMD without nfp-uio?
Thanks
