From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wang, Zhihong" <zhihong.wang@intel.com>, Ravi Kerur <rkerur@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v1 2/2] Test cases for rte_memcmp functions
Date: Mon, 02 Jan 2017 21:41:09 +0100 [thread overview]
Message-ID: <1828046.HL686xpgu5@xps13> (raw)
In-Reply-To: <8F6C2BD409508844A0EFC19955BE094110759EFE@SHSMSX103.ccr.corp.intel.com>
2016-06-07 11:09, Wang, Zhihong:
> From: Ravi Kerur [mailto:rkerur@gmail.com]
> > Zhilong, Thomas,
> >
> > If there is enough interest within DPDK community I can work on adding support
> > for 'unaligned access' and 'test cases' for it. Please let me know either way.
>
> Hi Ravi,
>
> This rte_memcmp is proved with better performance than glibc's in aligned
> cases, I think it has good value to DPDK lib.
>
> Though we don't have memcmp in critical pmd data path, it offers a better
> choice for applications who do.
Re-thinking about this series, could it be some values to have a rte_memcmp
implementation?
What is the value compared to glibc one? Why not working on glibc?
next prev parent reply other threads:[~2017-01-02 20:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 22:59 [PATCH v1 0/2] rte_memcmp functions Ravi Kerur
2016-03-07 23:00 ` [PATCH v1 1/2] rte_memcmp functions using Intel AVX and SSE intrinsics Ravi Kerur
2016-03-07 23:00 ` [PATCH v1 2/2] Test cases for rte_memcmp functions Ravi Kerur
2016-05-26 9:05 ` Wang, Zhihong
2016-06-06 18:31 ` Ravi Kerur
2016-06-07 11:09 ` Wang, Zhihong
2017-01-02 20:41 ` Thomas Monjalon [this message]
2017-01-09 5:29 ` Wang, Zhihong
2017-01-09 11:08 ` Thomas Monjalon
2017-01-11 1:28 ` Wang, Zhihong
2016-05-25 8:56 ` [PATCH v1 1/2] rte_memcmp functions using Intel AVX and SSE intrinsics Thomas Monjalon
2016-05-26 8:57 ` Wang, Zhihong
2018-12-20 23:30 ` Ferruh Yigit
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=1828046.HL686xpgu5@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rkerur@gmail.com \
--cc=zhihong.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.