From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: David Miller <davem@davemloft.net>
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [ANN] Unified dynamic storage for different socket types instead of separate hash tables.
Date: Thu, 22 Mar 2007 22:40:25 +0300 [thread overview]
Message-ID: <20070322194024.GA21378@2ka.mipt.ru> (raw)
In-Reply-To: <20070322.123604.70210071.davem@davemloft.net>
On Thu, Mar 22, 2007 at 12:36:04PM -0700, David Miller (davem@davemloft.net) wrote:
> > > 2) An extra list insert/delete to give list of all sockets
> >
> > That is too small price.
>
> In your imagination. Our connection rates went up significantly
> when I got rid of the linked list we had many years ago.
>
> Every memory access matters.
Ok, I never liked linked lists actually. :)
This one can be completely eliminated (hmm, it does not even exist so
far) by having per-node bitmask of used/free entries - it will be
even faster than existing access and will not require locks (due to RCU
protection).
So, this allows to remove additional hlist_node structure from socket
(and change netlink one to not use it in broadcasting, so for netlink
sockets it will be moved into private netlink structure).
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-03-22 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 18:09 [ANN] Unified dynamic storage for different socket types instead of separate hash tables Evgeniy Polyakov
2007-03-22 18:43 ` Stephen Hemminger
2007-03-22 18:59 ` Evgeniy Polyakov
2007-03-22 19:03 ` David Miller
2007-03-22 19:09 ` Evgeniy Polyakov
2007-03-22 19:14 ` David Miller
2007-03-22 19:20 ` Evgeniy Polyakov
2007-03-22 19:14 ` Evgeniy Polyakov
2007-03-22 19:21 ` David Miller
2007-03-22 19:30 ` Evgeniy Polyakov
2007-03-22 19:36 ` David Miller
2007-03-22 19:40 ` Evgeniy Polyakov [this message]
2007-03-27 14:23 ` Andi Kleen
2007-03-27 13:35 ` 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=20070322194024.GA21378@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.