DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pragash Vijayaragavan <pxv3620@rit.edu>
To: Andriy Berestovskyy <aber@semihalf.com>
Cc: dev@dpdk.org, Minseok Kwon <mxkvcs@rit.edu>
Subject: Re: [dpdk-dev] cuckoo hash in dpdk
Date: Thu, 24 Aug 2017 14:54:58 -0400	[thread overview]
Message-ID: <CANp7S23Tim2b1=uDs+GdpOanyqAQ7nR2jg1paKdU6=BpD--qOg@mail.gmail.com> (raw)
In-Reply-To: <CAOysbxp21_YfMsLP5dOLjyQpJyHFS3O7OS3JCXDZdNsb+K1e=A@mail.gmail.com>

Thats great, what about the hash functions.
On 24 Aug 2017 10:54, "Andriy Berestovskyy" <aber@semihalf.com> wrote:

> Hey Pragash,
> I am not the author of the code, but I guess it is done that way
> because modern compilers do recognize power of two constants and do
> substitute division and modulo operations with corresponding bit
> manipulations.
>
> Just try to compile a small program like the following:
>
> volatile unsigned a = 123, b, c;
> int main(int argc, char **argv)
> {
>     b = a / 4;
>     c = a % 4;
>     printf("%x %x %x\n", a, b, c);
> }
>
>
> and then disassemble it with gdb:
>
> (gdb) disassemble /s main
> [...]
> 13 b = a / 4;
>    0x0000000000400464 <+20>: shr    $0x2,%eax
>    0x0000000000400467 <+23>: mov    %eax,0x200bd3(%rip)        # 0x601040
> <b>
>
> 14 c = a % 4;
>    0x000000000040046d <+29>: mov    0x200bc5(%rip),%eax        # 0x601038
> <a>
>    0x0000000000400473 <+35>: and    $0x3,%eax
>    0x0000000000400476 <+38>: mov    %eax,0x200bc8(%rip)        # 0x601044
> <c>
> [...]
>
> As you can see both division and modulo was substituted with "shr" and
> "and".
>
> So basically nowadays there is no need to worry about that and
> complicate code with explicit low-level optimizations. Hope that
> answers your question.
>
> Regards,
> Andriy
>
>
> On Wed, Aug 23, 2017 at 4:15 PM, Pragash Vijayaragavan <pxv3620@rit.edu>
> wrote:
> > Hi,
> >
> > I got the chance to look at the cuckoo hash used in dpdk and have a
> query.
> >
> > would using division and modulo operations be slower than bitwise
> > operations on RTE_HASH_BUCKET_ENTRIES, specially since
> > RTE_HASH_BUCKET_ENTRIES is a power of 2.
> > For example, to do a modulo we can do a "AND" operation on
> > (RTE_HASH_BUCKET_ENTRIES - 1), which might be faster. We did a cuckoo
> > filter for VPP and doing this gave a slight improvement in speed.
> > Is there any particular reason its done this way.
> >
> > Sorry if i am being wrong in any way, i was just curious.
> >
> > Thanks,
> >
> > Pragash Vijayaragavan
> > Grad Student at Rochester Institute of Technology
> > email : pxv3620@rit.edu
> > ph : 585 764 4662
>
>
>
> --
> Andriy Berestovskyy
>

  reply	other threads:[~2017-08-24 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 14:15 Pragash Vijayaragavan
2017-08-23 18:28 ` Dumitrescu, Cristian
2017-08-23 20:20   ` Pragash Vijayaragavan
2017-08-23 20:39     ` Pragash Vijayaragavan
2017-08-24 14:53 ` Andriy Berestovskyy
2017-08-24 18:54   ` Pragash Vijayaragavan [this message]
2017-08-25  9:00     ` Andriy Berestovskyy

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='CANp7S23Tim2b1=uDs+GdpOanyqAQ7nR2jg1paKdU6=BpD--qOg@mail.gmail.com' \
    --to=pxv3620@rit.edu \
    --cc=aber@semihalf.com \
    --cc=dev@dpdk.org \
    --cc=mxkvcs@rit.edu \
    /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).