[dpdk-dev] doc: announce TILE-Gx removal
Checks
Commit Message
Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
doc/guides/rel_notes/deprecation.rst | 3 +++
1 file changed, 3 insertions(+)
Comments
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, February 13, 2017 10:53 AM
> To: Zhigang Lu <zlu@ezchip.com>; Liming Sun <lsun@ezchip.com>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: announce TILE-Gx removal
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index b49e0a0..d40b137 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -62,3 +62,6 @@ Deprecation Notices
> PMDs that implement the latter.
> Target release for removal of the legacy API will be defined once most
> PMDs have switched to rte_flow.
> +
> +* The architecture TILE-Gx and the associated mpipe driver are not
> + maintained and will be removed in 17.05.
The notification should probably be for removal in 17.08, to one release cycle to respond/fix/update.
It would also be good to hear from EZChip/Mellanox on this.
John
2017-02-14 08:50, Mcnamara, John:
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> > ---
> > doc/guides/rel_notes/deprecation.rst | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst
> > b/doc/guides/rel_notes/deprecation.rst
> > index b49e0a0..d40b137 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -62,3 +62,6 @@ Deprecation Notices
> > PMDs that implement the latter.
> > Target release for removal of the legacy API will be defined once most
> > PMDs have switched to rte_flow.
> > +
> > +* The architecture TILE-Gx and the associated mpipe driver are not
> > + maintained and will be removed in 17.05.
>
> The notification should probably be for removal in 17.08, to one release cycle to respond/fix/update.
There were some previous messages/warnings and there were no answer.
I have asked a working free toolchain, I did not have it.
We have asked some questions about drivers support, no reply.
I have asked about removal, no reply.
I really do not see why we should keep it longer.
> It would also be good to hear from EZChip/Mellanox on this.
They are mute since a long time on this topic.
Olga, do you confirm?
2017-02-14 09:58, Thomas Monjalon:
> 2017-02-14 08:50, Mcnamara, John:
> > The notification should probably be for removal in 17.08, to one release cycle to respond/fix/update.
>
> There were some previous messages/warnings and there were no answer.
> I have asked a working free toolchain, I did not have it.
> We have asked some questions about drivers support, no reply.
> I have asked about removal, no reply.
> I really do not see why we should keep it longer.
Some public links:
Recent warnings: http://dpdk.org/ml/archives/dev/2017-February/056981.html
Recent patch from Jerin without any comment: http://dpdk.org/commit/dff9071
Bug in 16.04 without any comment: https://mail-archive.com/dev@dpdk.org/msg31596.html
Work stopped in March, last year: https://mail-archive.com/dev@dpdk.org/msg43536.html
No update for free toolchain: https://mail-archive.com/dev@dpdk.org/msg42651.html
One year without any news is enough.
Hope it convinces you.
> > It would also be good to hear from EZChip/Mellanox on this.
>
> They are mute since a long time on this topic.
> Olga, do you confirm?
On Tue, Feb 14, 2017 at 10:28:39AM +0100, Thomas Monjalon wrote:
> 2017-02-14 09:58, Thomas Monjalon:
> > 2017-02-14 08:50, Mcnamara, John:
> > > The notification should probably be for removal in 17.08, to one release cycle to respond/fix/update.
> >
> > There were some previous messages/warnings and there were no answer.
> > I have asked a working free toolchain, I did not have it.
> > We have asked some questions about drivers support, no reply.
> > I have asked about removal, no reply.
> > I really do not see why we should keep it longer.
>
> Some public links:
> Recent warnings: http://dpdk.org/ml/archives/dev/2017-February/056981.html
> Recent patch from Jerin without any comment: http://dpdk.org/commit/dff9071
> Bug in 16.04 without any comment: https://mail-archive.com/dev@dpdk.org/msg31596.html
> Work stopped in March, last year: https://mail-archive.com/dev@dpdk.org/msg43536.html
> No update for free toolchain: https://mail-archive.com/dev@dpdk.org/msg42651.html
>
> One year without any news is enough.
> Hope it convinces you.
>
> > > It would also be good to hear from EZChip/Mellanox on this.
> >
> > They are mute since a long time on this topic.
> > Olga, do you confirm?
>
Regretfully, I must agree with Thomas on this. In the absense of a
response from someone to maintain this, it should be removed.
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
On Tue, Feb 14, 2017 at 10:50:19AM +0000, Bruce Richardson wrote:
> On Tue, Feb 14, 2017 at 10:28:39AM +0100, Thomas Monjalon wrote:
> > 2017-02-14 09:58, Thomas Monjalon:
> > > 2017-02-14 08:50, Mcnamara, John:
> > > > The notification should probably be for removal in 17.08, to one release cycle to respond/fix/update.
> > >
> > > There were some previous messages/warnings and there were no answer.
> > > I have asked a working free toolchain, I did not have it.
> > > We have asked some questions about drivers support, no reply.
> > > I have asked about removal, no reply.
> > > I really do not see why we should keep it longer.
> >
> > Some public links:
> > Recent warnings: http://dpdk.org/ml/archives/dev/2017-February/056981.html
> > Recent patch from Jerin without any comment: http://dpdk.org/commit/dff9071
> > Bug in 16.04 without any comment: https://mail-archive.com/dev@dpdk.org/msg31596.html
> > Work stopped in March, last year: https://mail-archive.com/dev@dpdk.org/msg43536.html
> > No update for free toolchain: https://mail-archive.com/dev@dpdk.org/msg42651.html
> >
> > One year without any news is enough.
> > Hope it convinces you.
> >
> > > > It would also be good to hear from EZChip/Mellanox on this.
> > >
> > > They are mute since a long time on this topic.
> > > Olga, do you confirm?
> >
>
> Regretfully, I must agree with Thomas on this. In the absense of a
> response from someone to maintain this, it should be removed.
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>
On Tue, 14 Feb 2017 10:50:19 +0000, Bruce Richardson
<bruce.richardson@intel.com> wrote:
> On Tue, Feb 14, 2017 at 10:28:39AM +0100, Thomas Monjalon wrote:
> > 2017-02-14 09:58, Thomas Monjalon:
> > > 2017-02-14 08:50, Mcnamara, John:
> > > > The notification should probably be for removal in 17.08, to
> > > > one release cycle to respond/fix/update.
> > >
> > > There were some previous messages/warnings and there were no
> > > answer. I have asked a working free toolchain, I did not have it.
> > > We have asked some questions about drivers support, no reply.
> > > I have asked about removal, no reply.
> > > I really do not see why we should keep it longer.
> >
> > Some public links:
> > Recent warnings:
> > http://dpdk.org/ml/archives/dev/2017-February/056981.html Recent
> > patch from Jerin without any comment:
> > http://dpdk.org/commit/dff9071 Bug in 16.04 without any comment:
> > https://mail-archive.com/dev@dpdk.org/msg31596.html Work stopped in
> > March, last year:
> > https://mail-archive.com/dev@dpdk.org/msg43536.html No update for
> > free toolchain: https://mail-archive.com/dev@dpdk.org/msg42651.html
> >
> > One year without any news is enough.
> > Hope it convinces you.
> >
> > > > It would also be good to hear from EZChip/Mellanox on this.
> > >
> > > They are mute since a long time on this topic.
> > > Olga, do you confirm?
> >
>
> Regretfully, I must agree with Thomas on this. In the absense of a
> response from someone to maintain this, it should be removed.
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
Same here.
Acked-by: Olivier Matz <olivier.matz@6wind.com>
On Tue, Feb 14, 2017 at 08:50:07AM +0000, Mcnamara, John wrote:
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Monday, February 13, 2017 10:53 AM
> > To: Zhigang Lu <zlu@ezchip.com>; Liming Sun <lsun@ezchip.com>
> > Cc: dev@dpdk.org
> > Subject: [dpdk-dev] [PATCH] doc: announce TILE-Gx removal
> >
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> > ---
> > doc/guides/rel_notes/deprecation.rst | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst
> > b/doc/guides/rel_notes/deprecation.rst
> > index b49e0a0..d40b137 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -62,3 +62,6 @@ Deprecation Notices
> > PMDs that implement the latter.
> > Target release for removal of the legacy API will be defined once most
> > PMDs have switched to rte_flow.
> > +
> > +* The architecture TILE-Gx and the associated mpipe driver are not
> > + maintained and will be removed in 17.05.
>
> The notification should probably be for removal in 17.08, to one release cycle to respond/fix/update.
>
> It would also be good to hear from EZChip/Mellanox on this.
>
> John
If - as seems likely - this deprecation notice makes it into the 17.02
release, I would just ask that the actual removal of the code *not* take
place at the start of the 17.05 release cycle, to be sure to give
further additional grace period for someone to respond to this. I think
it is only fair to wait till just before the RC's are produced to remove
the code, given it is such a drastic step, and the official notice of
removal is only inserted right before 17.02 goes out.
Regards,
/Bruce
> -----Original Message-----
> From: Richardson, Bruce
> Sent: Tuesday, February 14, 2017 11:25 AM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; Zhigang Lu
> <zlu@ezchip.com>; Liming Sun <lsun@ezchip.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: announce TILE-Gx removal
>
> On Tue, Feb 14, 2017 at 08:50:07AM +0000, Mcnamara, John wrote:
> >
> >
> > > -----Original Message-----
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > > Sent: Monday, February 13, 2017 10:53 AM
> > > To: Zhigang Lu <zlu@ezchip.com>; Liming Sun <lsun@ezchip.com>
> > > Cc: dev@dpdk.org
> > > Subject: [dpdk-dev] [PATCH] doc: announce TILE-Gx removal
> > >
> > > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> > > ---
> > > doc/guides/rel_notes/deprecation.rst | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/doc/guides/rel_notes/deprecation.rst
> > > b/doc/guides/rel_notes/deprecation.rst
> > > index b49e0a0..d40b137 100644
> > > --- a/doc/guides/rel_notes/deprecation.rst
> > > +++ b/doc/guides/rel_notes/deprecation.rst
> > > @@ -62,3 +62,6 @@ Deprecation Notices
> > > PMDs that implement the latter.
> > > Target release for removal of the legacy API will be defined once
> most
> > > PMDs have switched to rte_flow.
> > > +
> > > +* The architecture TILE-Gx and the associated mpipe driver are not
> > > + maintained and will be removed in 17.05.
> >
> > The notification should probably be for removal in 17.08, to one release
> cycle to respond/fix/update.
> >
> > It would also be good to hear from EZChip/Mellanox on this.
> >
> > John
>
> If - as seems likely - this deprecation notice makes it into the 17.02
> release, I would just ask that the actual removal of the code *not* take
> place at the start of the 17.05 release cycle, to be sure to give further
> additional grace period for someone to respond to this. I think it is only
> fair to wait till just before the RC's are produced to remove the code,
> given it is such a drastic step, and the official notice of removal is
> only inserted right before 17.02 goes out.
>
Hi,
That seems like a fair compromise.
John
On 02/14/2017 10:28 AM, Thomas Monjalon wrote:
> 2017-02-14 09:58, Thomas Monjalon:
>> 2017-02-14 08:50, Mcnamara, John:
>>> The notification should probably be for removal in 17.08, to one release cycle to respond/fix/update.
>>
>> There were some previous messages/warnings and there were no answer.
>> I have asked a working free toolchain, I did not have it.
>> We have asked some questions about drivers support, no reply.
>> I have asked about removal, no reply.
>> I really do not see why we should keep it longer.
>
> Some public links:
> Recent warnings: http://dpdk.org/ml/archives/dev/2017-February/056981.html
> Recent patch from Jerin without any comment: http://dpdk.org/commit/dff9071
> Bug in 16.04 without any comment: https://mail-archive.com/dev@dpdk.org/msg31596.html
> Work stopped in March, last year: https://mail-archive.com/dev@dpdk.org/msg43536.html
> No update for free toolchain: https://mail-archive.com/dev@dpdk.org/msg42651.html
>
> One year without any news is enough.
> Hope it convinces you.
It does for me:
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
As suggested by Bruce, let's remove it just before v17.05-rc1 to
let some time, even if they would already have replied in case they
had a plan for maintaining it.
Thanks,
Maxime
@@ -62,3 +62,6 @@ Deprecation Notices
PMDs that implement the latter.
Target release for removal of the legacy API will be defined once most
PMDs have switched to rte_flow.
+
+* The architecture TILE-Gx and the associated mpipe driver are not
+ maintained and will be removed in 17.05.