From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch 1/1] uml-update-2.6.8-finish
Date: Sat, 11 Sep 2004 14:15:50 -0400 [thread overview]
Message-ID: <20040911181550.GA2966@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200409111740.12121.blaisorblade_spam@yahoo.it>
On Sat, Sep 11, 2004 at 05:40:12PM +0200, BlaisorBlade wrote:
> And making it compile with the hash code, rather than the rb_tree one? I know
> ghash.h must be removed, but there is no reason at all to switch to Red-Black
> trees.
It is not just that ghash.h be removed. It is that its contents have
to vanish. That code shouldn't be anywhere.
There are good reasons to switch to rbtrees -
I need some sort of low-O lookup
there is no generic hash tree in the kernel
rbtree is O(lg n) and it's generic
rbtree is the only generic low-O lookup in the kernel that I see
I'm not in the fancy data structure business, so I'll stick with the
infrastructure that I find in the pool already, and rbtree is about it.
> Even because, later, we will just see "Hey, I get a panic here" +
> backtrace.
No, because currently there are no users of this. We can get this tested
when UML starts mmapping into its page cache.
> Doing things right in first place is better.
And inlining the grunge is right?
Jeff
next prev parent reply other threads:[~2004-09-11 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 17:38 [patch 1/1] uml-update-2.6.8-finish blaisorblade_spam
2004-09-10 18:59 ` [uml-devel] " BlaisorBlade
[not found] ` <200409102028.54580.blaisorblade_personal@yahoo.it>
[not found] ` <200409102103.i8AL3b0O004288@ccure.user-mode-linux.org>
2004-09-11 15:40 ` BlaisorBlade
2004-09-11 18:15 ` Jeff Dike [this message]
2004-09-11 17:47 ` BlaisorBlade
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=20040911181550.GA2966@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=linux-kernel@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