From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id A3960282 for ; Sat, 18 Feb 2017 10:30:00 +0100 (CET) Received: by mail-wm0-f46.google.com with SMTP id c85so35618416wmi.1 for ; Sat, 18 Feb 2017 01:30:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=CwNxvhStb3Fy9zGDCV16L/1UFOL7UlEGvu9lRdi2Fsc=; b=eWCCvsEMT88BAnAd6YXOvVe2l7hqQBwvmoNJQYuRztF7d5P2txsIUZSvVFe7FguNW5 w4tV27fAPDSvoqnhANsSsix+830ERjUs6eiWHFKjEsleBoGrni3HinUFHGZ50wtBnki8 25LeUhuXeNvH7/1d6SxjRQZoWWhmtGBxh061EDohxwKaEgotWfHgyIWm267qM6yvBwhY mwCAqIg4hFQmbI9vCsEIQUtCTV88vHUxd+5fzNurH/0geeJ/0AVCMSuilSxWPyKq+goS ePx4TqGgouZeQUTHnw7YZkLykpkW5BN0tuBXt8gm446nYYFoi5lmqLztrulAdUxm9m9T qwoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=CwNxvhStb3Fy9zGDCV16L/1UFOL7UlEGvu9lRdi2Fsc=; b=ZeDwklJ55d32b9+L1ci8EYm6H6esK49SsSw3P1QSDWLxtmIvxN2Ba7ODaorDvPq5dP A9Xcs4in2C360dYg5mW4z2UdbnjpQEI/XrSUbGKQHEp9VXc9TAf0jV51KIEfXnFrwzmG Xn98UjoHU9sWSPMrhWYeqkPdGgMSp+rRUj3OUhl3//YYvcAoRNr3zbCzJGmxBdHCniyk W86JL4WVWcUDBSokIMUZhfN+WSYyLAqKf9cudYN5IeUUwfMHa32UOAokUNuljhUFhXgW sKkawYTsvx1Ex2/aKQIwXmV7cuHe3LYak3Cy4LeG4q0kWGY3KL+tmcu0n5xgKqjyNRaD NJNQ== X-Gm-Message-State: AMke39kPUdIiWdLNEmMabuMtVy2v3UkoTl+09C8zFQli4fgynSgRReIHQQIOxdvmyAifXmdE X-Received: by 10.28.98.194 with SMTP id w185mr8829344wmb.84.1487410200350; Sat, 18 Feb 2017 01:30:00 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id z80sm8359922wrc.24.2017.02.18.01.29.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Feb 2017 01:29:59 -0800 (PST) From: Thomas Monjalon To: Chris Metcalf Cc: Vincent JARDIN , Bruce Richardson , Jerin Jacob , Olivier Matz , Liming Sun , Olga Shern , Yael Shenhav , dev@dpdk.org Date: Sat, 18 Feb 2017 10:29:58 +0100 Message-ID: <6894790.0dWopA5fmH@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <1487382749-9887-1-git-send-email-cmetcalf@mellanox.com> References: <1487382749-9887-1-git-send-email-cmetcalf@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Sat, 18 Feb 2017 09:30:00 -0000 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.