From: David Miller <davem@davemloft.net>
To: johnpol@2ka.mipt.ru
Cc: netdev@vger.kernel.org
Subject: Re: [1/1 take 2] Unified socket storage. (with small bench).
Date: Wed, 09 May 2007 03:02:00 -0700 (PDT) [thread overview]
Message-ID: <20070509.030200.123972145.davem@davemloft.net> (raw)
In-Reply-To: <20070509095740.GB10028@2ka.mipt.ru>
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Date: Wed, 9 May 2007 13:57:40 +0400
> That is only because we have very different way of working with udp.
> In udp hash table we can have multiple sockets bound to different ip
> addresses, but with the same port, so it will be placed into the same
> hash chain. With trie each socket will have differnet key, since
> addresses are different (or bound device number), so it automatically
> fixes problem with broken hash for udp (which is a bit fixed with
> extended hashing).
Yes it is power of trie.
So connection rates are interesting, but what about raw lookup
performance? Last time this topic came up you went into some
cave when you looked at the trie lookup assembly and compared
it to hash. :)
It does make more memory references than hash by definition, and we
need to figure out whether that matters enough or not.
next prev parent reply other threads:[~2007-05-09 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 17:43 [1/1 take 2] Unified socket storage. (with small bench) Evgeniy Polyakov
2007-05-09 6:48 ` David Miller
2007-05-09 9:34 ` Evgeniy Polyakov
2007-05-09 9:44 ` David Miller
2007-05-09 9:57 ` Evgeniy Polyakov
2007-05-09 10:02 ` David Miller [this message]
2007-05-09 10:22 ` Evgeniy Polyakov
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=20070509.030200.123972145.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--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).