From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20063.outbound.protection.outlook.com [40.107.2.63]) by dpdk.org (Postfix) with ESMTP id 4A7A02C50 for ; Mon, 20 Feb 2017 21:24:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=FSCVC6a/w3lT63eqrEVwujV4/21JXFdP4lRqyLCQBnI=; b=N2luLrjCbVHfvg6NoZHBqlGlYf0t4J1fSLFCYZ66ih5IhVu2fae8rtRG6ptu6cYxKEoIIGrzGrIWZdLm/4xfPwHE/l9c/kPXYAyL7olCqtH0L9dILeRpITcDZgWpijipGIv7aqI/In/r9NJ8BFm3/mZQp6lD0AJtp8+P41cpBjw= Received: from DB6PR0501MB2757.eurprd05.prod.outlook.com (10.172.226.9) by DB6PR0501MB2759.eurprd05.prod.outlook.com (10.172.226.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.13; Mon, 20 Feb 2017 20:24:43 +0000 Received: from DB6PR0501MB2757.eurprd05.prod.outlook.com ([10.172.226.9]) by DB6PR0501MB2757.eurprd05.prod.outlook.com ([10.172.226.9]) with mapi id 15.01.0919.015; Mon, 20 Feb 2017 20:24:43 +0000 From: Olga Shern To: Thomas Monjalon CC: Vincent JARDIN , Bruce Richardson , Jerin Jacob , Olivier Matz , Liming Sun , "Yael Shenhav" , "dev@dpdk.org" , Chris Metcalf Thread-Topic: [PATCH 0/4] catch up TILE-Gx support in DPDK Thread-Index: AQHSiYm5ojF/EsH3eU60/e0IKdl1uaFugBAAgANt2yA= Date: Mon, 20 Feb 2017 20:24:43 +0000 Message-ID: References: <1487382749-9887-1-git-send-email-cmetcalf@mellanox.com> <6894790.0dWopA5fmH@xps13> In-Reply-To: <6894790.0dWopA5fmH@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=olgas@mellanox.com; x-originating-ip: [77.126.53.236] x-ms-office365-filtering-correlation-id: 54565486-158f-4f2c-5c9a-08d459ce8172 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:DB6PR0501MB2759; x-microsoft-exchange-diagnostics: 1; DB6PR0501MB2759; 7:LZmrtpSstUX2O7etfU0ZmhzzGpHsmshS4vDp1y0E+lZX0pXW1Tklphylq7MX12nUd1Qs9JYtlkOK6KIesBJLHaNLcKsItOWZC6pcPWhqZJeFdR/W4V93zTxA6nOOFI26SXu+/OGocKhkvyKCXPCl50QICrX/YSi+9oCf15XSAVqBA78ma93xLyDWzjA7HESLmz1fXyYv3hREgWC5MEuOS9luQqOuABa7ljzoCbHg1ue4huBOgf3DOjv1V8J5gxfclIgJOR4uBD53KU2vh2p8KYZsAPjia7pW9w1ohp7BbrovYiy8eR+so11DsnsBoM7M2G/QVWIwP5FwZ2TbFORIUw== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(171992500451332)(228905959029699); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123555025)(20161123560025)(20161123562025)(20161123564025)(6072148); SRVR:DB6PR0501MB2759; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0501MB2759; x-forefront-prvs: 02243C58C6 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39410400002)(39450400003)(39860400002)(39840400002)(39850400002)(199003)(377424004)(189002)(377454003)(13464003)(2906002)(50986999)(54356999)(76176999)(4326007)(68736007)(2900100001)(54906002)(53546006)(229853002)(189998001)(97736004)(966004)(5660300001)(66066001)(99286003)(2950100002)(55016002)(92566002)(7696004)(9686003)(6916009)(6306002)(31430400001)(8676002)(102836003)(6116002)(7736002)(74316002)(101416001)(81166006)(3846002)(86362001)(81156014)(305945005)(25786008)(53936002)(77096006)(38730400002)(122556002)(8936002)(33656002)(107886003)(105586002)(106356001)(106116001)(3280700002)(6506006)(110136004)(6436002)(3660700001)(6246003); DIR:OUT; SFP:1101; SCL:1; SRVR:DB6PR0501MB2759; H:DB6PR0501MB2757.eurprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2017 20:24:43.2910 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0501MB2759 Subject: Re: [dpdk-dev] [PATCH 0/4] catch up TILE-Gx support in DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 20:24:45 -0000 Hi Thomas, All Mellanox agrees to remove TILE-Gx support from DPDK.org, but will continue = to support customers using DPDK.=20 Customer that needs support should contact Mellanox directly. Best Regards, Olga > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Saturday, February 18, 2017 11: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 >=20 > 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. >=20 > 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 th= e > future (lessons learned). >=20 > > 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. >=20 > So do you mean that the TILE-Gx maintainers officially give up on their r= ole? > Then please update the MAINTAINERS file. >=20 > > 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. >=20 > I agree. We can apply these patches before removing the whole > architecture. >=20 > > 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). >=20 > I think it is OK as is.