From: Mike Sowka <msowka@gmail.com>
To: dev@dpdk.org
Cc: Mike Sowka <msowka@gmail.com>
Subject: [dpdk-dev] [PATCH] sched: fix build on Atom without SSE4 support
Date: Sat, 5 Dec 2015 00:00:56 -0500 [thread overview]
Message-ID: <1449291656-4900-2-git-send-email-msowka@gmail.com> (raw)
In-Reply-To: <1449291656-4900-1-git-send-email-msowka@gmail.com>
---
lib/librte_sched/rte_sched.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/librte_sched/rte_sched.c b/lib/librte_sched/rte_sched.c
index 21ebf25..6f92aa6 100644
--- a/lib/librte_sched/rte_sched.c
+++ b/lib/librte_sched/rte_sched.c
@@ -55,8 +55,8 @@
#ifdef RTE_SCHED_VECTOR
#include <rte_vect.h>
-#if defined(__SSE2__)
-#define SCHED_VECTOR_SSE2
+#if defined(__SSE4__)
+#define SCHED_VECTOR_SSE4
#endif
#endif
@@ -1672,7 +1672,7 @@ grinder_schedule(struct rte_sched_port *port, uint32_t pos)
return 1;
}
-#ifdef SCHED_VECTOR_SSE2
+#ifdef SCHED_VECTOR_SSE4
static inline int
grinder_pipe_exists(struct rte_sched_port *port, uint32_t base_pipe)
--
2.1.0
next prev parent reply other threads:[~2015-12-05 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 5:00 [dpdk-dev] [PATCH] " Mike Sowka
2015-12-05 5:00 ` Mike Sowka [this message]
2015-12-05 21:07 ` [dpdk-dev] [PATCH] sched: " Thomas Monjalon
2015-12-05 22:27 Mike Sowka
2015-12-05 23:47 ` 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=1449291656-4900-2-git-send-email-msowka@gmail.com \
--to=msowka@gmail.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).