DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH v2 0/3] fix build issues with librte_sched, test_red on non x86 platform
Date: Sun, 30 Aug 2015 14:25:19 +0530	[thread overview]
Message-ID: <1440924922-11156-1-git-send-email-jerin.jacob@caviumnetworks.com> (raw)

This patch set enable librte_sched, app/test/test_sched and app/test/test_red
to build on non x86 platform

v1..v2  use memory barrier version rte_rdtsc() for multi arch support as
suggested by Thomas Monjalon

Jerin Jacob (3):
  sched: remove unused inclusion of tmmintrin.h
  app/test: test_sched: fix needless build dependency on
    CONFIG_RTE_ARCH_X86_64
  app/test: use memory barrier version of rte_rdtsc() eal api for multi
    arch support

 app/test/Makefile             |  2 +-
 app/test/test_red.c           | 11 +----------
 lib/librte_sched/rte_bitmap.h |  3 ---
 3 files changed, 2 insertions(+), 14 deletions(-)

-- 
2.1.0

             reply	other threads:[~2015-08-30  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30  8:55 Jerin Jacob [this message]
2015-08-30  8:55 ` [dpdk-dev] [PATCH 1/3] sched: remove unused inclusion of tmmintrin.h Jerin Jacob
2015-08-30  8:55   ` [dpdk-dev] [PATCH 2/3] app/test: test_sched: fix needless build dependency on CONFIG_RTE_ARCH_X86_64 Jerin Jacob
2015-08-30  8:55     ` [dpdk-dev] [PATCH 3/3] app/test: use memory barrier version of rte_rdtsc() eal api for multi arch support Jerin Jacob
2015-09-08  7:19 ` [dpdk-dev] [PATCH v2 0/3] fix build issues with librte_sched, test_red on non x86 platform 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=1440924922-11156-1-git-send-email-jerin.jacob@caviumnetworks.com \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    /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).