From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <cmetcalf@mellanox.com> Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0077.outbound.protection.outlook.com [104.47.1.77]) by dpdk.org (Postfix) with ESMTP id 916CA98 for <dev@dpdk.org>; Tue, 21 Feb 2017 19:15:19 +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=bb1nQgcTFw0200IDvtqZjhinKCgmkpvu9ycKf/GKYG8=; b=MOxzL3uCgaUOhJHngiSq82iJRFsDwohZeqhoqnY0GJ2RtgC6oiJ/ILZXPWXbBncMSQqv0ag4KB+8fyju9D8C9SCp1ndLfXGT4xMLSbYn0qJYX6AVQFdhy+6lBbuHZOV29Do/RqqYmXZ+DN/a97lmrpGDUt767sd5rA1c/oi4P3g= Received: from HE1PR0501MB2764.eurprd05.prod.outlook.com (10.172.125.18) by HE1PR0501MB2761.eurprd05.prod.outlook.com (10.172.125.15) 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 18:15:18 +0000 Received: from HE1PR0501MB2764.eurprd05.prod.outlook.com ([10.172.125.18]) by HE1PR0501MB2764.eurprd05.prod.outlook.com ([10.172.125.18]) with mapi id 15.01.0919.015; Tue, 21 Feb 2017 18:15:18 +0000 From: Chris Metcalf <cmetcalf@mellanox.com> To: Liming Sun <lsun@mellanox.com> CC: Thomas Monjalon <thomas.monjalon@6wind.com>, 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> Thread-Topic: [PATCH 0/4] catch up TILE-Gx support in DPDK Thread-Index: AQHSiYm6OAwejHUYfUSqdHSmBBb/dKFugBAAgAUiYwCAACdi6g== Date: Tue, 21 Feb 2017 18:15:17 +0000 Message-ID: <C168B628-E180-4219-A58A-4B3C8BE9D261@mellanox.com> References: <1487382749-9887-1-git-send-email-cmetcalf@mellanox.com> <6894790.0dWopA5fmH@xps13>, <HE1PR0501MB2427A78E9F5C4B3DDD8C6E05A1510@HE1PR0501MB2427.eurprd05.prod.outlook.com> In-Reply-To: <HE1PR0501MB2427A78E9F5C4B3DDD8C6E05A1510@HE1PR0501MB2427.eurprd05.prod.outlook.com> 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=cmetcalf@mellanox.com; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [108.60.230.202] x-ms-office365-filtering-correlation-id: a110a572-d617-4203-c125-08d45a859735 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:HE1PR0501MB2761; x-microsoft-exchange-diagnostics: 1; HE1PR0501MB2761; 7:nXSjbMKjg52Xw1Vq9LNtJrUwrL/UZaSxTuJPPEXvTCoWSIYQ6kTOehgkB5uMIKN6iLkXjM+LVBi7GJ3KIUL1H+MuWhY9XKw9iargJgx1fYteToKRQkYsSMZVKqQfXxBX7J6BJAkC1fp75XXvj5zW1yLIJjjMdQEvyQg6wnhDlvj74f4rJBASCSG9T6gsIUs2M7WzKfym1khgR9jdZNZ6jlKmqIA59IlY6QfJNOlrXLqysgokXnaFY1gdAAdMO84GxzhaiIH70meCWXfqm1vpYsvClaO+/AAM4lAFdV6NM1cT596K683ZjzzOyfg8fW1hlkD+zjbnr47jTn4V5ZU7gw== x-microsoft-antispam-prvs: <HE1PR0501MB2761500A97A028EE57F919DFB2510@HE1PR0501MB2761.eurprd05.prod.outlook.com> 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:HE1PR0501MB2761; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0501MB2761; x-forefront-prvs: 0225B0D5BC x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39840400002)(39450400003)(39860400002)(39850400002)(39410400002)(13464003)(199003)(24454002)(377424004)(377454003)(189002)(101416001)(6486002)(8676002)(106356001)(77096006)(229853002)(106116001)(81156014)(105586002)(82746002)(54356999)(8936002)(76176999)(50986999)(122556002)(81166006)(66066001)(99286003)(6506006)(53936002)(33656002)(6636002)(6306002)(6436002)(54906002)(25786008)(2950100002)(5660300001)(31430400001)(6512007)(102836003)(83716003)(53546006)(97736004)(2900100001)(86362001)(2906002)(305945005)(966004)(36756003)(7736002)(68736007)(92566002)(4326007)(3280700002)(3660700001)(6246003)(6862004)(38730400002)(189998001)(110136004)(3846002)(6116002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0501MB2761; H:HE1PR0501MB2764.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 18:15:17.7573 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0501MB2761 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 <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 21 Feb 2017 18:15:19 -0000 Lining please go ahead since you are the maintainer. Note I adjusted mainta= iners in my patch so probably best to wait for that series to be applied th= en just remove the maintainers entry along with all the tilegx mpipe stuff.= =20 Sent from the waterpark while waiting for a kid :) On Feb 21, 2017, at 10:54 AM, Liming Sun <lsun@mellanox.com> wrote: >>> So do you mean that the TILE-Gx maintainers officially give up on their= role? >>> Then please update the MAINTAINERS file. >=20 > Yes. Please update the MAINTAINERS file as needed. > Chris Metcalf is out this week. I could submit a separate patch for the M= AINTAINERS file if it's required. Or we could wait a little bit until Chris= comes back. >=20 > Thanks, > Liming >=20 > -----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 S= un; 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. >>=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. >=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 w= on't allow any new component in DPDK which cannot be built freely, in the f= uture (lessons learned). >=20 >> 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 = 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=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. >=20 > I agree. We can apply these patches before removing the whole architectur= e. >=20 >> 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). >=20 > I think it is OK as is. >=20