From: Ravi Kerur <rkerur@gmail.com>
To: "Wang, Zhihong" <zhihong.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-dev, v3] Implement memcmp using Intel SIMD instrinsics.
Date: Tue, 23 Feb 2016 20:00:54 -0800 [thread overview]
Message-ID: <CAFb4SLCZ4vCVWw5xNhjeLi0SFuOndmP+hnYhrCqbr0gD_7bxsg@mail.gmail.com> (raw)
In-Reply-To: <8F6C2BD409508844A0EFC19955BE0941033C7CA2@SHSMSX103.ccr.corp.intel.com>
On Tue, Feb 23, 2016 at 4:22 AM, Wang, Zhihong <zhihong.wang@intel.com>
wrote:
> > > It'd be great if you could format this patch into a patch set with
> several
> > > little ones. :-)
> > > Also, the kernel checkpatch is very helpful.
> > > Good coding style and patch organization make it easy for in-depth
> reviews.
> > >
> > Combination of scalar and vector (32/64/128) was done to get optimal
> performance numbers. If there is enough interest in this I can work on it
> and provide an updated patch set.
>
> That'll be very helpful! Looking forward to your patch :)
> BTW, have you tested real example performance with your patch?
>
Yes it was tested with hash functions in dpdk code.I will work on it and
send updated patch. Thanks for your inputs I will incorporate them in next
patch series.
next prev parent reply other threads:[~2016-02-24 4:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 20:01 [dpdk-dev] [PATCH v3] Implement memcmp using SIMD intrinsics Ravi Kerur
2015-05-18 20:01 ` [dpdk-dev] [PATCH v3] Implement memcmp using Intel SIMD instrinsics Ravi Kerur
2015-10-14 0:32 ` Stephen Hemminger
2016-01-28 3:08 ` [dpdk-dev] [dpdk-dev, " Zhihong Wang
2016-02-19 17:50 ` Ravi Kerur
2016-02-23 12:22 ` Wang, Zhihong
2016-02-24 4:00 ` Ravi Kerur [this message]
2015-06-12 8:30 ` [dpdk-dev] [PATCH v3] Implement memcmp using SIMD intrinsics Ondřej Bílka
2015-06-12 9:03 ` Bruce Richardson
2015-06-15 20:47 ` Ravi Kerur
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=CAFb4SLCZ4vCVWw5xNhjeLi0SFuOndmP+hnYhrCqbr0gD_7bxsg@mail.gmail.com \
--to=rkerur@gmail.com \
--cc=dev@dpdk.org \
--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 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).