From: William Lee Irwin III <wli@holomorphy.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Daniel Ritz <daniel.ritz@gmx.ch>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
daniel.ritz@alcatel.ch, Robert Love <rml@tech9.net>
Subject: Re: [PATCH 2.5] speedup kallsyms_lookup
Date: Fri, 10 Jan 2003 08:03:34 -0800 [thread overview]
Message-ID: <20030110160334.GU23814@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301101428420.1292-100000@localhost.localdomain>
On Fri, Jan 10, 2003 at 03:29:19PM +0000, Hugh Dickins wrote:
> I hope I can leave this discussion to others: I just wanted to get
> my symbols printing out right, and noticed the current stem compression
> unnecessarily weak there; but I'm no expert on suitable algorithms.
I can help some here but probably no more than you (in fact, you've
spotted far more [> 0] issues with the current code than I).
Basically, if you want fast string lookup of compressed stuff I can sit
down with whiteboard etc. and fiddle around, but it sounds like from f's
comments that this isn't really wanted.
So the end-result of the discussion is, "What should really happen here?"
and "What, if anything, do you want me to do?"
Bill
next prev parent reply other threads:[~2003-01-10 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 9:53 [PATCH 2.5] speedup kallsyms_lookup Daniel Ritz
2003-01-10 15:29 ` Hugh Dickins
2003-01-10 16:03 ` William Lee Irwin III [this message]
2003-01-10 16:12 ` Andi Kleen
2003-01-10 16:13 ` William Lee Irwin III
2003-01-10 16:34 ` Hugh Dickins
2003-01-10 17:15 ` Robert Love
2003-01-10 19:44 ` Daniel Ritz
2003-01-10 16:37 ` Zwane Mwaikambo
2003-01-10 17:13 ` Valdis.Kletnieks
2003-01-10 17:19 ` Andi Kleen
2003-01-10 19:01 ` Randy.Dunlap
2003-01-11 4:28 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 4:14 Albert D. Cahalan
2003-01-11 5:33 ` William Lee Irwin III
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=20030110160334.GU23814@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=daniel.ritz@alcatel.ch \
--cc=daniel.ritz@gmx.ch \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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