From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Vladimir Medvedkin <medvedkinv@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Make the thash library arch-independent
Date: Tue, 28 Jul 2015 15:47:57 +0200 [thread overview]
Message-ID: <1831659.nSDl63dTav@xps13> (raw)
In-Reply-To: <1438088792-16344-1-git-send-email-medvedkinv@gmail.com>
Hi Vladimir,
Thanks for fixing.
Comments below.
2015-07-28 09:06, Vladimir Medvedkin:
> Signed-off-by: Vladimir Medvedkin <medvedkinv@gmail.com>
Please explain how it was broken and how you fixed it.
It would be interesting to know which part is __SSE3__ and __SSE__.
> +#ifdef __SSE3__
> +#include <rte_vect.h>
> +#endif /* __SSE3__ */
Comments after short ifdef block are not needed.
> +#ifndef XMM_SIZE
> +#define XMM_SIZE 16
Why is it needed?
next prev parent reply other threads:[~2015-07-28 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:06 Vladimir Medvedkin
2015-07-28 13:47 ` Thomas Monjalon [this message]
2015-07-28 15:33 ` Vladimir Medvedkin
2015-07-28 16:05 ` Thomas Monjalon
2015-07-28 19:08 ` Vladimir Medvedkin
2015-07-29 13:56 ` [dpdk-dev] [PATCH v2] " Vladimir Medvedkin
2015-07-29 23:40 ` 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=1831659.nSDl63dTav@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=medvedkinv@gmail.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).