From: Liming Sun <lsun@mellanox.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Chris Metcalf <cmetcalf@mellanox.com>
Cc: Vincent JARDIN <vincent.jardin@6wind.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Olivier Matz <olivier.matz@6wind.com>,
Olga Shern <olgas@mellanox.com>,
"Yael Shenhav" <yaeli@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] catch up TILE-Gx support in DPDK
Date: Tue, 21 Feb 2017 15:54:20 +0000 [thread overview]
Message-ID: <HE1PR0501MB2427A78E9F5C4B3DDD8C6E05A1510@HE1PR0501MB2427.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <6894790.0dWopA5fmH@xps13>
>> So do you mean that the TILE-Gx maintainers officially give up on their role?
>> Then please update the MAINTAINERS file.
Yes. Please update the MAINTAINERS file as needed.
Chris Metcalf is out this week. I could submit a separate patch for the MAINTAINERS file if it's required. Or we could wait a little bit until Chris comes back.
Thanks,
Liming
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Saturday, February 18, 2017 4:30 AM
To: Chris Metcalf
Cc: Vincent JARDIN; Bruce Richardson; Jerin Jacob; Olivier Matz; Liming Sun; Olga Shern; Yael Shenhav; dev@dpdk.org
Subject: Re: [PATCH 0/4] catch up TILE-Gx support in DPDK
2017-02-17 20:52, Chris Metcalf:
> This patch series allows DPDK to build for TILE-Gx as of version 17.02.
>
> A required library (libgxio) had not been made publicly available.
> It is now available as source here:
>
>
> http://www.mellanox.com/repository/solutions/tile-scm/libgxio-1.0.tar.
> xz
>
> it has also been folded into the binary release of the generic
> toolchain that we periodically update on that website; for more
> information about the toolchain tarballs, see here:
>
> http://www.mellanox.com/repository/solutions/tile-scm/
>
> Note that the toolchain components were updated slightly in this
> release of the tarballs relative to what was there before.
Thank you.
Some of these changes (being able to compile on a free toolchain) should have been done since the beginning. Better later than never :) I think we won't allow any new component in DPDK which cannot be built freely, in the future (lessons learned).
> Hopefully, with DPDK now working on TILE-Gx again, there may be
> interest from someone in the community in taking on a maintenance
> role. At this point, the Mellanox engineering team responsible for
> TILE-Gx is largely focused on working on future chips based on ARMv8,
> so unfortunately we won't have much bandwidth for TILE-Gx support going forward.
So do you mean that the TILE-Gx maintainers officially give up on their role?
Then please update the MAINTAINERS file.
> If it still seems like removal makes sense now or at some point in the
> future, it would probably at least be good to apply these patches so
> there is a baseline to pick it up from later.
I agree. We can apply these patches before removing the whole architecture.
> Liming Sun, the tile dpdk maintainer, has reviewed these changes (he
> sits next to me); if it's more appropriate, he can resend these
> changes with his Signed-off-by as well. I took on this work since I
> was more familiar with libgxio and the details of our toolchain (I am
> the maintainer for the tile architecture for Linux and glibc).
I think it is OK as is.
next prev parent reply other threads:[~2017-02-21 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 1:52 Chris Metcalf
2017-02-18 1:52 ` [dpdk-dev] [PATCH 1/4] tile: avoid use of non-upstreamed <arch/cycle.h> Chris Metcalf
2017-02-18 1:52 ` [dpdk-dev] [PATCH 2/4] tile: remove requirement for <arch/mpipe_{xaui, gbe}_def.h headers Chris Metcalf
2017-02-18 1:52 ` [dpdk-dev] [PATCH 3/4] strict alignment: generalize warning handling Chris Metcalf
2017-02-18 1:52 ` [dpdk-dev] [PATCH 4/4] tile: fix remaining build issues Chris Metcalf
2017-02-18 9:29 ` [dpdk-dev] [PATCH 0/4] catch up TILE-Gx support in DPDK Thomas Monjalon
2017-02-20 20:24 ` Olga Shern
2017-02-21 9:14 ` Bruce Richardson
2017-02-21 15:54 ` Liming Sun [this message]
2017-02-21 18:15 ` Chris Metcalf
2017-02-27 15:36 ` 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=HE1PR0501MB2427A78E9F5C4B3DDD8C6E05A1510@HE1PR0501MB2427.eurprd05.prod.outlook.com \
--to=lsun@mellanox.com \
--cc=bruce.richardson@intel.com \
--cc=cmetcalf@mellanox.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=olgas@mellanox.com \
--cc=olivier.matz@6wind.com \
--cc=thomas.monjalon@6wind.com \
--cc=vincent.jardin@6wind.com \
--cc=yaeli@mellanox.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 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).