DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"Wodkowski, PawelX" <pawelx.wodkowski@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 09:23:16 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725821420FC7@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <20150423081138.GA8592@bricha3-MOBL3>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Thursday, April 23, 2015 9:12 AM
> To: Wodkowski, PawelX
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] Implement memcmp using AVX/SSE instructio
> 
> On Thu, Apr 23, 2015 at 09:24:52AM +0200, Pawel Wodkowski wrote:
> > On 2015-04-22 17:33, Ravi Kerur wrote:
> > >+/**
> > >+ * Compare bytes between two locations. The locations must not overlap.
> > >+ *
> > >+ * @note This is implemented as a macro, so it's address should not be taken
> > >+ * and care is needed as parameter expressions may be evaluated multiple times.
> > >+ *
> > >+ * @param src_1
> > >+ *   Pointer to the first source of the data.
> > >+ * @param src_2
> > >+ *   Pointer to the second source of the data.
> > >+ * @param n
> > >+ *   Number of bytes to compare.
> > >+ * @return
> > >+ *   true if equal otherwise false.
> > >+ */
> > >+static inline bool
> > >+rte_memcmp(const void *src_1, const void *src,
> > >+		size_t n) __attribute__((always_inline));
> > You are exposing this as public API, so I think you should follow
> > description bellow or not call this _memcmp_
> >
> > int memcmp(const void *s1, const void *s2, size_t n);
> >
> > The memcmp() function returns an integer less than, equal  to,  or greater
> > than
> >        zero  if  the  first  n  bytes  of s1 is found, respectively, to be
> > less than, to
> >        match, or be greater than the first n bytes of s2.
> >
> 
> +1 to this point.
> 
> 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?

Yep, same thought here, is it really worth it?
Konstantin

> 
> /Bruce
> 
> > --
> > Pawel

  parent reply	other threads:[~2015-04-23  9:23 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
2015-04-23  9:23       ` Ananyev, Konstantin [this message]
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=2601191342CEEE43887BDE71AB97725821420FC7@irsmsx105.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=pawelx.wodkowski@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).