public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: rwhron@earthlink.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Rik spreading bullshit about VM
Date: Thu, 17 Jan 2002 14:08:41 -0500	[thread overview]
Message-ID: <200201171908.OAA02671@gatekeeper.tmr.com> (raw)
In-Reply-To: <20020116202640.A485@earthlink.net>

In article <20020116202640.A485@earthlink.net> you write:
| About running the Andrea VM in 4M:
| I booted in single user mode.
| 
| bash-2.05a# uname -a
| Linux mountain 2.4.18pre2aa2 #1 Wed Jan 9 21:44:03 EST 2002 i586 unknown
| 
| bash-2.05a# dmesg| grep mem
| Kernel command line: BOOT_IMAGE=2418p2aa2 ro root=1602 console=ttyS1,38400n8 single mem=4m
| Memory: 2100k/4096k available (891k kernel code, 1608k reserved, 215k data, 196k init, 0k highmem)
| Freeing unused kernel memory: 196k freed

	[...snip...]

| I've tested a bunch of kernels lately.  This is only what's sitting in /boot
| since I last cleaned it out:
| 
| mountain:/boot$ ls vml*
| vmlinuz                  vmlinuz-2.4.17rc2aa2-old  vmlinuz-2.4.18-pre3         
| vmlinuz-2.4.18pre2       vmlinuz-2.4.18pre3ll      vmlinuz-2.5.1-dj11  
| vmlinuz-2.5.2-pre10      vmlinuz-2.5.2-pre9        vmlinuz-2.4.17
| vmlinuz-2.4.17rc2aa2-wli vmlinuz-2.4.18-pre4       vmlinuz-2.4.18pre2aa1
| vmlinuz-2.4.18pre3pe     vmlinuz-2.5.1-dj13        vmlinuz-2.5.2-pre11
| vmlinuz-2.5.2-pre9mingo  vmlinuz-2.4.17-rmap11a    vmlinuz-2.4.17rmap11b
| vmlinuz-2.4.18pre1-mjc2nio vmlinuz-2.4.18pre2aa2   vmlinuz-2.4.18pre3pelb
| vmlinuz-2.5.1-dj14       vmlinuz-2.5.2-pre5        vmlinuz.old
| vmlinuz-2.4.17rc2aa2    vmlinuz-2.4.18-pre1        vmlinuz-2.4.18pre1mjc2
| vmlinuz-2.4.18pre3-ac2  vmlinuz-2.5.1              vmlinuz-2.5.2
| vmlinuz-2.5.2-pre6-mingo
| 
| IMHO, 2.4.18pre2aa2 is the best!

  Of the current kernels it may well be, I have tried it on two largish
machines and it worked "right," I'm building it on a small and slow
machine to try that. However, I was not happy with the default bdflush
settings, and people who don't see what they want should use the
expanded capabilities of -aa before complaining. Also, the performance
I've seen so far, and I have NOT run a full set of tests, would
indicate that it is slightly better than 2.4.13-acN (N is 5, 7 or 8,
don't have it on this machine).

  I am looking forward to testing on many configs, and just for the
extra tuning tools in bdflush I think it will be good on all of them.
As I posted before, I think the best scheduler is the one which doesn't
have "jackpot cases" which produce really bad performance. With a
little tuning I believe -aa is there.

  Finally, that said I'm trying a patch of my own to -aa, which is why
I haven't run the full set of tests, there are two things I think will
make it even better, and I am finally getting to understand the code,
little as I wanted to.

  I can't disagree with Rik on the VM in the unpatched kernel for
several months. It really was not good, and both the -ac and -aa kernels
were taking aim at that problem. IMHO the changes went in before the
bugs went out. Needless to say Rik should not apply for a job as a
diplomat, but I can't disagree with the existance of a problem. If RH
uses a custom VM he was factual about that, although there may be
several reasons for the choice.

  Maybe we could deflect the pissing contest back to technical
discussion now?
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  reply	other threads:[~2002-01-17 19:09 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17  1:26 Rik spreading bullshit about VM rwhron
2002-01-17 19:08 ` bill davidsen [this message]
2002-01-17 19:49   ` Rik van Riel
2002-01-17 20:22     ` Dan Chen
  -- strict thread matches above, loose matches on Subject: below --
2002-01-17  4:01 rwhron
2002-01-17  1:16 Andrea Scrimieri
2002-01-17  0:08 V-man
2002-01-17  0:31 ` Rik van Riel
2002-01-17  7:44   ` Luigi Genoni
2002-01-17 11:11     ` Rik van Riel
2002-01-17 15:25   ` John Jasen
2002-01-16 21:49 Dieter Nützel
     [not found] <Pine.LNX.4.33L.0201162235480.32617-100000@imladris.surriel .com>
2002-01-16 19:04 ` Andrea Arcangeli
2002-01-16 20:11   ` Jose Luis Domingo Lopez
2002-01-16 20:58   ` Richard Gooch
2002-01-16 21:10     ` Dave Jones
2002-01-16 21:17       ` Rik van Riel
2002-01-17  0:20       ` Luigi Genoni
2002-01-16 21:17     ` Craig Knox
2002-01-16 20:58   ` Bongani Hlope
2002-01-16 20:55     ` John Levon
2002-01-16 21:21       ` Bongani Hlope
2002-01-16 21:29   ` Adam Kropelin
2002-01-16 21:58   ` Diego Calleja
2002-01-16 22:02     ` Rik van Riel
2002-01-16 21:59   ` Diego Calleja
2002-01-16 22:44   ` Chris Chabot
2002-01-17  8:18     ` Christoph Rohland
2002-01-17  0:07   ` Erik Mouw
2002-01-17  0:25     ` J Sloan
2002-01-17  1:15       ` Erik Mouw
2002-01-17 17:40       ` bill davidsen
2002-01-17 14:14     ` Alan Cox
2002-01-18  4:30     ` Bosko Radivojevic
2002-01-17  0:38   ` Rik van Riel
2002-01-17  1:50     ` Nicolas Pitre
2002-01-17 11:45       ` Rik van Riel
2002-01-17 12:02         ` Stephan von Krawczynski
2002-01-17  2:14     ` Andrea Scrimieri
2002-01-17 12:07       ` Rik van Riel
2002-01-17 13:11         ` Andrea Scrimieri
2002-01-17 13:15           ` Rik van Riel
2002-01-17 14:02             ` Alan Cox
2002-01-17 21:41             ` Trever L. Adams
2002-01-18  1:46               ` brian
2002-01-17  1:52   ` Stephen Satchell
2002-01-17 13:26   ` Alan Cox

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=200201171908.OAA02671@gatekeeper.tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwhron@earthlink.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