From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0059.outbound.protection.outlook.com [104.47.0.59]) by dpdk.org (Postfix) with ESMTP id 88A95379B for ; Tue, 21 Feb 2017 16:54:22 +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=QQinyt0zJF8GSkBfVRBuRtV0RfQiD+YW1v/oarG8KZk=; b=FyRQN5/1UJMNrHhb8sw3SHgwyeU3SEZHIwtsHiIV/L+Q0lXOAb/TPSWE0Pag4oaZ+yOGolcqJetRRk+Q7I8AQOc/mPUMseSOYZG6FZCrDDkLZDLA6Hbzkkd8U6vHsAfaHezaZEgEqYDmDJiwMNpbt3nYEmoNIBvsPvA1ar4RbF8= Received: from HE1PR0501MB2427.eurprd05.prod.outlook.com (10.168.126.7) by HE1PR0501MB2763.eurprd05.prod.outlook.com (10.172.125.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.13; Tue, 21 Feb 2017 15:54:20 +0000 Received: from HE1PR0501MB2427.eurprd05.prod.outlook.com ([10.168.126.7]) by HE1PR0501MB2427.eurprd05.prod.outlook.com ([10.168.126.7]) with mapi id 15.01.0919.018; Tue, 21 Feb 2017 15:54:20 +0000 From: Liming Sun To: Thomas Monjalon , Chris Metcalf CC: Vincent JARDIN , Bruce Richardson , Jerin Jacob , Olivier Matz , Olga Shern , "Yael Shenhav" , "dev@dpdk.org" Thread-Topic: [PATCH 0/4] catch up TILE-Gx support in DPDK Thread-Index: AQHSicmWp0Rd3DnIk0amsbseDlKwNKFzoJIg Date: Tue, 21 Feb 2017 15:54:20 +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=lsun@mellanox.com; x-originating-ip: [12.216.194.146] x-ms-office365-filtering-correlation-id: 71785357-e8f6-44c4-5106-08d45a71e644 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:HE1PR0501MB2763; x-microsoft-exchange-diagnostics: 1; HE1PR0501MB2763; 7:OHfB3NJWlbt5KljBhPBF19CmSsRZowa5R9031npkkNoo5EQJu/DH8CgBZYv83Wh0bop4wpEzRcmU6xX42I2Fc6Uw5Ci7kZ7qk/KaYh3w5YExNvSSDZ4n5rADk4U7ju+gVLstBYu3tdzgQ/1mH7ipptndNaIw3R2sm6LblIICgnheudZOT3wzCw/s2rrc1B7z2nLMEIK51wkVLPlmZqgylScr3pA34FcHppB6rD45waO3UqShC4VNZCen984olUws0nq2gQe/1Iw4TXEQ0CyDXMrVyKa4iL1Uwt2WGR1lf7pL5zalWGPTgQKZPD918QWPo6aHKtTtGWEvWmSRQGH+bA== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(171992500451332); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123560025)(20161123558025)(20161123564025)(20161123562025)(20161123555025)(6072148); SRVR:HE1PR0501MB2763; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0501MB2763; x-forefront-prvs: 0225B0D5BC x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(39860400002)(39840400002)(39410400002)(39850400002)(377424004)(377454003)(13464003)(199003)(189002)(101416001)(54356999)(50986999)(3660700001)(122556002)(189998001)(3280700002)(966004)(38730400002)(8936002)(6506006)(76176999)(8676002)(6246003)(97736004)(53546006)(53936002)(2900100001)(81156014)(81166006)(31430400001)(86362001)(3846002)(74316002)(106116001)(106356001)(4326007)(66066001)(7696004)(92566002)(6636002)(7736002)(305945005)(77096006)(105586002)(5660300001)(2906002)(68736007)(102836003)(9686003)(25786008)(55016002)(6116002)(6306002)(54906002)(99286003)(229853002)(6436002)(33656002)(2950100002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0501MB2763; H:HE1PR0501MB2427.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: 21 Feb 2017 15:54:20.4611 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0501MB2763 X-Mailman-Approved-At: Thu, 23 Feb 2017 09:50:36 +0100 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: Tue, 21 Feb 2017 15:54:22 -0000 >> 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 MAI= NTAINERS file if it's required. Or we could wait a little bit until Chris c= omes back. Thanks, Liming -----Original Message----- From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]=20 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. >=20 > A required library (libgxio) had not been made publicly available. > It is now available as source here: >=20 > =20 > http://www.mellanox.com/repository/solutions/tile-scm/libgxio-1.0.tar. > xz >=20 > it has also been folded into the binary release of the generic=20 > toolchain that we periodically update on that website; for more=20 > information about the toolchain tarballs, see here: >=20 > http://www.mellanox.com/repository/solutions/tile-scm/ >=20 > Note that the toolchain components were updated slightly in this=20 > 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 ha= ve 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 fut= ure (lessons learned). > Hopefully, with DPDK now working on TILE-Gx again, there may be=20 > interest from someone in the community in taking on a maintenance=20 > role. At this point, the Mellanox engineering team responsible for=20 > TILE-Gx is largely focused on working on future chips based on ARMv8,=20 > so unfortunately we won't have much bandwidth for TILE-Gx support going f= orward. So do you mean that the TILE-Gx maintainers officially give up on their rol= e? Then please update the MAINTAINERS file. > If it still seems like removal makes sense now or at some point in the=20 > future, it would probably at least be good to apply these patches so=20 > 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=20 > sits next to me); if it's more appropriate, he can resend these=20 > changes with his Signed-off-by as well. I took on this work since I=20 > was more familiar with libgxio and the details of our toolchain (I am=20 > the maintainer for the tile architecture for Linux and glibc). I think it is OK as is.