From: "Buddy Lumpkin" <blumpkin@attbi.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Adam McKenna" <adam-dated-1013023458.e87e05@flounder.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: should I trust 'free' or 'top'?
Date: Fri, 1 Feb 2002 23:18:30 -0800 [thread overview]
Message-ID: <FJEIKLCALBJLPMEOOMECMECBCFAA.blumpkin@attbi.com> (raw)
In-Reply-To: <E16Wjpi-0005w7-00@the-village.bc.nu>
>The only kernels you are likely to see that not happen on are
>- The 2.4.9 kernel with Rik's patches that Linus didnt take
(Red Hat 2.4.9-*)
>- 2.4.17/18pre with the rmap11/rmap12 patches
>- 2.4.17/18pre with the -aa patched VM
(which I believe is also in the SuSE kernel packages)
>- 2.2
>The base VM in Linus tree has been broken since before 2.4.0 and while
>somewhat better is still that - broken. The major vendors don't ship it for
>a reason.
Why is this?
Is linus working toward what he believes will be a better impementation? Is
he just being stubborn?
I guess I just can't imagine any reason why he would want
large enterprise applications running poorly when there are obvious fixes.
Believe it or not, im not trying to start a flame war, just trying to
understand the logic.
--Buddy
next prev parent reply other threads:[~2002-02-02 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 19:24 Adam McKenna
2002-02-01 19:50 ` Peter Makholm
2002-02-01 19:58 ` Alan Cox
2002-02-02 7:18 ` Buddy Lumpkin [this message]
2002-02-02 17:09 ` Denis Vlasenko
2002-02-02 17:11 ` Alan Cox
2002-02-02 19:58 ` David Lang
2002-02-02 20:35 ` Alan Cox
2002-02-01 20:11 ` William Lee Irwin III
2002-02-01 20:32 ` Adam McKenna
2002-02-01 21:41 ` William Lee Irwin III
2002-02-04 9:41 Martin Knoblauch
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=FJEIKLCALBJLPMEOOMECMECBCFAA.blumpkin@attbi.com \
--to=blumpkin@attbi.com \
--cc=adam-dated-1013023458.e87e05@flounder.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome