From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinj@marvell.com>
Cc: 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>,
maxime.coquelin@redhat.com, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH] doc: announce the deprecation of legacy virtio support
Date: Mon, 25 May 2020 01:44:00 +0200 [thread overview]
Message-ID: <1673507.n9d9JF5DbN@thomas> (raw)
In-Reply-To: <20200523140750.3967959-1-jerinj@marvell.com>
23/05/2020 16:07, jerinj@marvell.com:
> From: Jerin Jacob <jerinj@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.coquelin@redhat.com
> Cc: david.marchand@redhat.com
> Signed-off-by: Jerin Jacob <jerinj@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?
> + More details at http://patches.dpdk.org/patch/69351/
next prev parent reply other threads:[~2020-05-24 23:44 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 of legacy virtio support jerinj
2020-05-24 23:44 ` Thomas Monjalon [this message]
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
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=1673507.n9d9JF5DbN@thomas \
--to=thomas@monjalon.net \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.