DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luke Gorrie <luke@snabb.co>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] Implement memcmp using AVX/SSE instructio
Date: Thu, 23 Apr 2015 10:21:16 +0200	[thread overview]
Message-ID: <CAA2XHbfKpt8zDM_LteCxa9gqnJVoVP2fSFCC6oj_E6fAGXA4Bw@mail.gmail.com> (raw)
In-Reply-To: <20150423081138.GA8592@bricha3-MOBL3>

On 23 April 2015 at 10:11, Bruce Richardson <bruce.richardson@intel.com>
wrote:

> Also, if I read your quoted performance numbers in your earlier mail
> correctly,
> we are only looking at a 1-4% performance increase. Is the additional code
> to
> maintain worth the benefit?
>

... and if so, how would one decide whether it is better to to add this to
DPDK vs contribute it to GNU libc?

Pawel noted that this is not compatible with memcmp(3). It is very similar
to the legacy function bcmp(3) though so perhaps libc would accept it as
such.

Cheers,
-Luke

  reply	other threads:[~2015-04-23  8:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 15:33 [dpdk-dev] [PATCH] Implement rte_memcmp with AVX/SSE instructions Ravi Kerur
2015-04-22 15:33 ` [dpdk-dev] [PATCH] Implement memcmp using AVX/SSE instructio Ravi Kerur
2015-04-23  7:24   ` Pawel Wodkowski
2015-04-23  8:11     ` Bruce Richardson
2015-04-23  8:21       ` Luke Gorrie [this message]
2015-04-23  9:23       ` Ananyev, Konstantin
2015-04-23 13:53         ` Ravi Kerur
2015-04-23 14:00           ` Bruce Richardson
2015-04-23 22:26             ` Ravi Kerur
2015-05-05 21:56               ` Ravi Kerur
2015-04-23 13:43     ` 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=CAA2XHbfKpt8zDM_LteCxa9gqnJVoVP2fSFCC6oj_E6fAGXA4Bw@mail.gmail.com \
    --to=luke@snabb.co \
    --cc=bruce.richardson@intel.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).