From: Jerin Jacob <jerinjacobk@gmail.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
Ray Kinsella <mdr@ashroe.eu>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce the removal of legacy virtio support
Date: Mon, 25 May 2020 13:22:20 +0530 [thread overview]
Message-ID: <CALBAE1NODqvZS3Dwe=6D0qFOrAZHLUj8ccVFBkTcFfKSE7=OeA@mail.gmail.com> (raw)
In-Reply-To: <25d32839-a0e9-5d47-1354-a330c5d49831@redhat.com>
On Mon, May 25, 2020 at 1:03 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> Hi Jerrin,
Hi Maxime,
>
> I think what was agreed wasn't to remove Legacy Virtio support,
> but instead remove support for probing legacy Virtio devices when they
> are not bound to any Kernel drivers.
>
> It should still be possible to use these legacy Virtio devices when
> bound to VFIO or UIO.
I was not aware that legacy virtio can be used with VFIO or UIO.
I will send the v3.
>
> Regards,
> Maximle
>
> On 5/25/20 7:46 AM, jerinj@marvell.com wrote:
> > From: Jerin Jacob <jerinj@marvell.com>
> >
> > The legacy virtio feature 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 removal will also optimize DPDK PCI enumeration
> > management as it does not need to probe RTE_KDRV_NONE based
> > devices anymore.
> >
> > Legacy virtio feature removal is planned in the v20.11 release.
> >
> > More details at http://patches.dpdk.org/patch/69351/
> >
> > Cc: maxime.coquelin@redhat.com
> > Cc: david.marchand@redhat.com
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> > ---
> > doc/guides/rel_notes/deprecation.rst | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> > index cf8b1eb7b..79a03432c 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -107,3 +107,11 @@ Deprecation Notices
> > Python 2 support will be completely removed in 20.11.
> > In 20.08, explicit deprecation warnings will be displayed when running
> > scripts with Python 2.
> > +
> > +* virtio: The legacy virtio feature 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 removal will also optimize DPDK PCI enumeration management as
> > + it does not need to probe RTE_KDRV_NONE based devices anymore.
> > + Legacy virtio feature removal is planned in the v20.11 release.
> > + More details at http://patches.dpdk.org/patch/69351/
> >
>
next prev parent reply other threads:[~2020-05-25 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 14:07 [dpdk-dev] [PATCH] doc: announce the deprecation " jerinj
2020-05-24 23:44 ` Thomas Monjalon
2020-05-25 5:37 ` Jerin Jacob
2020-05-25 5:46 ` [dpdk-dev] [PATCH v2] doc: announce the removal " jerinj
2020-05-25 7:33 ` Maxime Coquelin
2020-05-25 7:52 ` Jerin Jacob [this message]
2020-05-25 8:15 ` [dpdk-dev] [PATCH v3] doc: announce the removal of RTE_KDRV_NONE based probe jerinj
2020-05-25 8:20 ` Maxime Coquelin
2020-05-26 14:44 ` Olivier Matz
2020-05-26 15:04 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALBAE1NODqvZS3Dwe=6D0qFOrAZHLUj8ccVFBkTcFfKSE7=OeA@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).