From: Kurt H Maier <khm@sciops.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Git/fs: Possibly Usable
Date: Wed, 3 Apr 2019 17:34:27 -0700 [thread overview]
Message-ID: <20190404003427.GA90432@wopr> (raw)
In-Reply-To: <CAJSxfmKdBt-k3k2yKQcctKjasj+D_bmNkjiq0Siie2-i3kqWJw@mail.gmail.com>
On Wed, Apr 03, 2019 at 05:00:15PM -0700, Skip Tavakkolian wrote:
> 9front maintainers, can anyone speak to technical reasons for creating a
> new version rather than fixing existing? Also, any thoughts on changing the
> name slightly so they can both be on the same system? maybe libAVL?
In 2016 spew wrote libbst, which is a binary search tree library that
supports both AVL and left-leaning red-black tree. While he was at it
he wrote a faster and simpler avl implementation, and fixed venti and
nupas to work with it. Since those were the only two things in the tree
that used AVL, nobody really cared if the old implementation went away.
I'm not sure what the advantage is to reintroducing it to 9front (aside
from the desire for zen-garden reliquaries). The programs that use the
old API can be counted on one hand and fixing them is not difficult.
The question was raised, at the time, if the old one might have been
hand-tuned for some venti-related performance characteristics, but I
don't think anyone followed through on measuring the difference. If
there are such idiosyncracies in the old code, they were not documented.
khm
next prev parent reply other threads:[~2019-04-04 0:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 4:41 ori
2019-04-02 6:10 ` Skip Tavakkolian
2019-04-02 13:32 ` Dave MacFarlane
2019-04-02 14:37 ` Kyohei Kadota
2019-04-03 10:38 ` Giacomo
2019-04-03 18:29 ` Skip Tavakkolian
2019-04-03 20:14 ` David du Colombier
2019-04-03 20:23 ` Ori Bernstein
2019-04-04 0:00 ` Skip Tavakkolian
2019-04-04 0:34 ` Kurt H Maier [this message]
2019-04-04 1:22 ` Ori Bernstein
2019-04-14 9:58 ` [9fans] UI design | enhancements Darren Wise
2019-04-14 11:30 ` Ethan Gardener
2019-04-14 14:19 ` hiro
2019-04-15 5:07 ` Lucio De Re
2019-04-15 6:12 ` Bakul Shah
2019-04-15 6:25 ` Devine Lu Linvega
2019-04-15 6:41 ` Michael Misch
2019-04-15 7:24 ` Bakul Shah
2019-04-15 11:20 ` hiro
2019-04-15 14:27 ` Kurt H Maier
2019-04-15 19:59 ` Ethan Gardener
2019-04-15 20:04 ` Michael Misch
2019-04-15 15:10 ` Chris McGee
2019-04-15 15:44 ` Darren Wise
2019-04-15 18:11 ` ab
2019-07-08 19:54 ` [9fans] Git/fs: Possibly Usable Ori Bernstein
2019-07-12 18:27 ` Patrick Marchand
2019-07-12 20:21 ` Steve Simon
2019-07-21 21:06 ` clueelf
2019-07-25 21:59 ` Ori Bernstein
2019-08-05 18:43 ` Skip Tavakkolian
2019-08-05 21:17 ` erik quanstrom
2019-08-05 21:22 ` erik quanstrom
2019-08-09 5:56 ` Ori Bernstein
2019-04-02 5:36 cinap_lenrek
2019-04-02 15:35 ori
2019-04-03 16:02 ori
2019-04-03 16:59 ` Giacomo
2019-04-03 18:41 ` Cull
2019-04-03 18:44 ` Ori Bernstein
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=20190404003427.GA90432@wopr \
--to=khm@sciops.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).