netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: david.lebrun@uclouvain.be, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next] ipv6: implement consistent hashing for equal-cost multipath routing
Date: Thu, 01 Dec 2016 15:26:38 -0500 (EST)	[thread overview]
Message-ID: <20161201.152638.37238894730380417.davem@davemloft.net> (raw)
In-Reply-To: <1480511568.3649771.803688521.5B47BE8F@webmail.messagingengine.com>

From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Wed, 30 Nov 2016 14:12:48 +0100

> David, one question: do you remember if you measured with linked lists
> at that time or also with arrays. I actually would expect small arrays
> that entirely fit into cachelines to be actually faster than our current
> approach, which also walks a linked list, probably the best algorithm to
> trash cache lines. I ask because I currently prefer this approach more
> than having large allocations in the O(1) case because of easier code
> and easier management.

I did not try this and I do agree with you that for extremely small table
sizes a list or array would perform better because of the cache behavior.

      reply	other threads:[~2016-12-01 20:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 19:59 [RFC PATCH net-next] ipv6: implement consistent hashing for equal-cost multipath routing David Lebrun
2016-11-28 16:22 ` David Miller
2016-11-28 20:16   ` David Lebrun
2016-11-28 20:32     ` David Miller
2016-11-28 20:58       ` David Lebrun
2016-11-30 13:12       ` Hannes Frederic Sowa
2016-12-01 20:26         ` David Miller [this message]

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=20161201.152638.37238894730380417.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=david.lebrun@uclouvain.be \
    --cc=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.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).