DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@mellanox.com>
To: 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>,
	Liming Sun <lsun@mellanox.com>, Olga Shern <olgas@mellanox.com>,
	Yael Shenhav <yaeli@mellanox.com>,
	dev@dpdk.org
Cc: Chris Metcalf <cmetcalf@mellanox.com>
Subject: [dpdk-dev] [PATCH 0/4] catch up TILE-Gx support in DPDK
Date: Fri, 17 Feb 2017 20:52:25 -0500	[thread overview]
Message-ID: <1487382749-9887-1-git-send-email-cmetcalf@mellanox.com> (raw)

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.

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.

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.

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).

Chris Metcalf (4):
  tile: avoid use of non-upstreamed <arch/cycle.h>
  tile: remove requirement for <arch/mpipe_{xaui,gbe}_def.h headers
  strict alignment: generalize warning handling
  tile: fix remaining build issues

 config/defconfig_tile-tilegx-linuxapp-gcc          |  1 -
 drivers/net/mpipe/mpipe_tilegx.c                   | 36 ++++++++++++++--------
 lib/librte_eal/common/arch/tile/rte_cpuflags.c     |  3 --
 .../common/include/arch/tile/rte_cycles.h          |  4 +--
 mk/arch/tile/rte.vars.mk                           |  5 +++
 mk/toolchain/gcc/rte.vars.mk                       |  4 +--
 6 files changed, 33 insertions(+), 20 deletions(-)

-- 
2.7.2

             reply	other threads:[~2017-02-18  1:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18  1:52 Chris Metcalf [this message]
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
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=1487382749-9887-1-git-send-email-cmetcalf@mellanox.com \
    --to=cmetcalf@mellanox.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=lsun@mellanox.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).