From: Andi Kleen <ak@suse.de>
To: Robert Olsson <Robert.Olsson@data.slu.se>
Cc: netdev@vger.kernel.org, snilsson@nada.kth.se
Subject: Re: Paper on lookup in Linux.
Date: Mon, 4 Sep 2006 15:29:39 +0200 [thread overview]
Message-ID: <200609041529.39688.ak@suse.de> (raw)
In-Reply-To: <17660.8632.602340.514616@robur.slu.se>
On Monday 04 September 2006 14:53, Robert Olsson wrote:
> No we haven't put struct socket in the leafs (result node) yet we just kept
> dst entries and some stateful flow variables that we used for active GC
> and flow logging so far. So 128 bit flow version of the dst hash. It would
> have taken a lot a of more work and we wanted to get this paper out. Also
> ip_route_input is not the place have the lookup if we with unified include
> ip6. So we focused on designing and building the lookup core.
Thanks.
The reason I'm asking is that we still have trouble with the TCP hash tables
taking far too much memory, and your new data structure might provide a nice
alternative.
-Andi
next prev parent reply other threads:[~2006-09-04 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 11:43 Paper on lookup in Linux Robert Olsson
2006-09-04 12:24 ` Andi Kleen
2006-09-04 12:53 ` Robert Olsson
2006-09-04 13:29 ` Andi Kleen [this message]
2006-09-04 13:54 ` Robert Olsson
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=200609041529.39688.ak@suse.de \
--to=ak@suse.de \
--cc=Robert.Olsson@data.slu.se \
--cc=netdev@vger.kernel.org \
--cc=snilsson@nada.kth.se \
/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).