From: David Woodhouse <dwmw2@redhat.com>
Cc: "John Hall" <John.Hall@optionexist.co.uk>,
"Linux MTD list (E-mail)" <linux-mtd@lists.infradead.org>
Subject: Re: Stable cvs version for 2.4
Date: Wed, 04 Sep 2002 01:18:02 +0100 [thread overview]
Message-ID: <21107.1031098682@redhat.com> (raw)
In-Reply-To: <16232.1031056191@redhat.com>
dwmw2@infradead.org said:
> The head of CVS as of yesterday (cvs up -D yesterday) should be fine.
> Don't use the stuff I committed at 1 o'clock this morning without
> testing it. That would not be advisable :)
The current code now seems to be passing my stress tests again. I think I
may have ironed out the rbtree bugs. So anyone who was previously
complaining that the performance went to pot after files got quite large,
suck this one and see. Should now have O(log N) lookup and insertion costs
instead of O(N), N obviously being the size of the file.
You may have to nab a copy of lib/rbtree.c from a vaguely recent 2.4 kernel
if you're using ancient ones, or maybe just export its contents. I'm going
to clean that up later; I don't like the existing one because it wastes
sizeof(int) for a single bit of colour information which could easily be
packed into the low bits of one of the pointers. :)
--
dwmw2
next prev parent reply other threads:[~2002-09-04 0:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 10:09 Stable cvs version for 2.4 John Hall
2002-09-03 12:29 ` David Woodhouse
2002-09-04 0:18 ` David Woodhouse [this message]
2002-09-04 1:14 ` Jasmine Strong
2002-09-04 8:51 ` David Woodhouse
2002-09-04 14:21 ` Jasmine Strong
2002-09-04 14:37 ` David Woodhouse
2002-09-04 14:46 ` Allen Curtis
2002-09-04 14:54 ` Jasmine Strong
2002-09-04 15:17 ` Steve Wahl
2002-09-04 15:26 ` David Woodhouse
2002-09-04 15:20 ` David Woodhouse
2002-09-04 15:33 ` Jasmine Strong
2002-09-04 15:44 ` David Woodhouse
2002-09-04 15:50 ` Allen Curtis
2002-09-04 15:54 ` David Woodhouse
2002-09-04 14:49 ` Jasmine Strong
2002-09-04 15:06 ` David Woodhouse
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=21107.1031098682@redhat.com \
--to=dwmw2@redhat.com \
--cc=John.Hall@optionexist.co.uk \
--cc=linux-mtd@lists.infradead.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