From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: patha@ida.liu.se
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: "fuzzy hashing" = skiplists in a different shape
Date: Fri, 28 Aug 1998 14:06:33 -0700 [thread overview]
Message-ID: <199808282106.OAA06177@dm.cobaltmicro.com> (raw)
In-Reply-To: <199808280906.LAA13808@portofix.ida.liu.se> (message from Patrik Hagglund on Fri, 28 Aug 1998 11:06:33 +0200)
Date: Fri, 28 Aug 1998 11:06:33 +0200
From: Patrik Hagglund <patha@ida.liu.se>
? What is this common case. I can't see how your implementation would
be faster than a good implementation of a balanced search tree.
You said the answer, I don't have to balance anything, so
insert/delete don't cost so much like trees requiring balancing do.
I would suggest that people run through some examples, ie. take
/proc/{pid}/maps for some large process with many attachments, like
emacs or something, have a little test program setup the data
structures as if vma_insert was called in sequence for each vma, and
then pick arbitrary addresses and see what find_vma() does and how
quickly it finds the answer.
Or just print little ascii visualiziations from your test program and
try to figure out for yourself with the picture it outputs why it is
so impressive an algorithm and why it kicks the shit out of any tree
based solution for this class of problems.
Later,
David S. Miller
davem@dm.cobaltmicro.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
prev parent reply other threads:[~1998-08-28 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-28 9:06 "fuzzy hashing" = skiplists in a different shape Patrik Hagglund
1998-08-28 21:06 ` David S. 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=199808282106.OAA06177@dm.cobaltmicro.com \
--to=davem@dm.cobaltmicro.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=patha@ida.liu.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