On Mon, May 25, 2020 at 5:14 AM Thomas Monjalon <tho...@monjalon.net> wrote: > > 23/05/2020 16:07, jer...@marvell.com: > > From: Jerin Jacob <jer...@marvell.com> > > > > The legacy virtio is not architecture agnostics. > > It relies on x86 IO port scheme support for its working. > > The legacy virtio is only the consumer of RTE_KDRV_NONE in the DPDK > > PCI subsystem. Legacy virtio deprecation will also optimize DPDK PCI > > enumeration management as it does not need to probe RTE_KDRV_NONE based > > devices anymore. > > > > Deprecation is planned for v20.08 release. > > > > More details at http://patches.dpdk.org/patch/69351/ > > > > Cc: maxime.coque...@redhat.com > > Cc: david.march...@redhat.com > > Signed-off-by: Jerin Jacob <jer...@marvell.com> > > --- > > --- a/doc/guides/rel_notes/deprecation.rst > > +++ b/doc/guides/rel_notes/deprecation.rst > > +* virtio: The legacy virtio is not architecture agnostics. > > + It relies on x86 IO port scheme support for its working. > > + The legacy virtio is only the consumer of RTE_KDRV_NONE in DPDK PCI > > subsystem. > > + Legacy virtio deprecation will also optimize DPDK PCI enumeration > > management as > > + it does not need to probe RTE_KDRV_NONE based devices anymore. > > + Deprecation is planned for v20.08 release. > > What means deprecation exactly? > When the feature is going to be removed?
I will change the wording. I think, we can target the removal in 20.11 release. > > > + More details at http://patches.dpdk.org/patch/69351/ > > >
