From: Larry McVoy <lm@bitmover.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
Ion Badulescu <ionut@cs.columbia.edu>,
Keith Owens <kaos@ocs.com.au>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: KBuild 2.5 Impressions
Date: Thu, 30 May 2002 17:32:19 -0700 [thread overview]
Message-ID: <20020530173219.X30298@work.bitmover.com> (raw)
In-Reply-To: <E17DZCa-0007hI-00@starship> <Pine.LNX.4.44.0205301704550.23527-100000@dlang.diginsite.com>
On Thu, May 30, 2002 at 05:09:16PM -0700, David Lang wrote:
> don't forget that the kbuild2.5 patch was a lot smaller before keith was
> told to "go away and don't bother anyone until the speed problem is fixed"
> a large part of the fix was to use the mmapped db stuff that Larry McVoy
> made available instead of useing the standard db libraries on the system.
wc mdbm.c
1404 4736 32921 mdbm.c
Just for the record. MDBM certainly has limitations, but being too many lines
of code is not one of them. And it provides ndbm/dbm compat interfaces so
you can pull it out and drop in something else if you like.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-05-31 0:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 9:45 KBuild 2.5 Impressions Daniel Phillips
2002-05-30 12:50 ` Martin Dalecki
2002-05-30 14:08 ` Kenneth Johansson
2002-05-30 13:28 ` Paul P Komkoff Jr
2002-05-30 21:55 ` Ion Badulescu
2002-05-30 22:29 ` Thunder from the hill
2002-05-30 23:19 ` Daniel Phillips
2002-05-31 0:09 ` David Lang
2002-05-31 0:29 ` Daniel Phillips
2002-05-31 0:32 ` Larry McVoy [this message]
2002-06-03 7:21 ` Rusty Russell
2002-05-31 0:13 ` Kenneth Johansson
2002-05-31 0:47 ` Daniel Phillips
2002-05-31 1:20 ` Skip Ford
2002-05-31 1:24 ` Daniel Phillips
2002-05-31 13:48 ` Tomas Szepe
2002-05-31 14:28 ` Nicolas Pitre
2002-05-31 15:21 ` Thunder from the hill
[not found] ` <Pine.LNX.4.44.0205302129120.29405-100000@hawkeye.luckynet.adm>
2002-05-31 4:01 ` Skip Ford
2002-05-31 4:46 ` KBuild 2.5 Migration Daniel Phillips
2002-05-31 5:12 ` Skip Ford
2002-05-31 0:48 ` KBuild 2.5 Impressions Nicolas Pitre
2002-05-31 3:29 ` Hua Zhong
2002-05-31 3:39 ` Daniel Phillips
2002-05-31 3:55 ` Thunder from the hill
2002-06-02 4:03 ` Ion Badulescu
2002-06-02 6:51 ` Daniel Phillips
2002-06-02 7:58 ` Thunder from the hill
2002-06-02 14:03 ` Sam Ravnborg
2002-06-02 14:38 ` Daniel Phillips
2002-06-02 14:56 ` Sam Ravnborg
2002-06-02 15:05 ` Thunder from the hill
2002-06-02 15:16 ` Daniel Phillips
2002-06-02 18:26 ` Sam Ravnborg
2002-06-02 18:39 ` Thunder from the hill
2002-06-02 18:57 ` Ion Badulescu
2002-06-02 19:15 ` Thunder from the hill
2002-06-03 2:04 ` Kai Germaschewski
2002-06-02 15:47 ` Thunder from the hill
2002-06-02 11:21 ` Peter Osterlund
2002-06-02 11:37 ` Thunder from the hill
2002-06-02 11:53 ` Peter Osterlund
2002-06-02 12:03 ` Thunder from the hill
2002-06-02 12:09 ` Thunder from the hill
2002-06-02 12:51 ` Peter Osterlund
2002-06-02 14:00 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 2:49 Dan Kegel
2002-06-03 3:28 ` Linus Torvalds
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=20020530173219.X30298@work.bitmover.com \
--to=lm@bitmover.com \
--cc=david.lang@digitalinsight.com \
--cc=ionut@cs.columbia.edu \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=torvalds@transmeta.com \
/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