From: jfm2@club-internet.fr
To: H.H.vanRiel@phys.uu.nl
Cc: jfm2@club-internet.fr, linux-mm@kvack.org
Subject: Re: Two naive questions and a suggestion
Date: 20 Nov 1998 01:25:24 -0000 [thread overview]
Message-ID: <19981120012524.5136.qmail@sidney.remcomp.fr> (raw)
In-Reply-To: <Pine.LNX.3.96.981119210154.16706B-100000@mirkwood.dummy.home> (message from Rik van Riel on Thu, 19 Nov 1998 21:05:35 +0100 (CET))
>
> On 19 Nov 1998 jfm2@club-internet.fr wrote:
>
> > 1) Is there any text describing memory management in 2.1? (Forgive me
> > if I missed an obvious URL)
>
> Not yet, I really should be working on that (the code
> seems to have stabilized now)...
>
> > 2) Are there plans for implementing the swapping of whole processes a
> > la BSD?
>
> Yes, there are plans. The plans are quite detailed too, but
> I think I haven't put them up on my home page yet.
>
This will close the gap between Linux and *BSDs at high loads. It
will also close the mouthes of some BSD people who talk loudly about
what areas where BSD is superior and carefully forget SMP, Elf or
modules to name just a few areas where Linux got it first.
> > Suggestion: Given that the requiremnts for a workstation (quick
> > response) are different than for a server (high throughput) it could
> > make sense to allow the user either use /proc for selecting the VM
> > policy or have a form of loadable VM manager. Or select it at
> > compile time.
>
> There are quite a lot of things you can tune in /proc,
> I don't know if you have read the documentation, but
> if you start trying things you'll be amazed hom much
> you can change the system's behaviour with the existing
> controls.
>
I have read a bit about them but sometimes changing the algorythm is
the right thing to do.
> Btw, since you are so enthusiastic about documentation,
> would you be willing to help me write it?
>
I could try to help you but it will be limited help. I already work
on a project of "Linux for normal people" and I also wanted to write
an article about optimizing a Linux box. The goal is to smash the
myth about kernel compiling. Why? Because in 95 my brother in law
needed a computer for his thesis in Spanish litterature. I remebered
kernel compiling and I led him to Apple Expo. That day one thing was
clear: Linux will never reach world domination as long as litterature
professors cannot use it and as long as kernel compiling be necessary
or even recommended then Linux will be off limits for litterature
professors.
So I scanned the source code in 2.0.34 and found the unsignificant
differences between code compiled for Pentiums and 386. Then I
compiled the Byte benchmark using the same compile flags used for the
386 kernels and the ones for Pentiums and PPros. Difference in speed
was < 2 % both on a real Pentium and on a K6. So much for "it will
allow you to tune to the processor".
About memory savings. First of all in 98 distributors shipping
crippled kernels should be shot: modular 2.0 has been around for over
two years. Also modularity has reduced the memory savings you get
from recompiling the kernel (if the distributor did a good job) qwhile
machines got bigger: over 1.5 Megs saved on an 8 Meg box are
significant (1.2.13 in 95), 500K on a 32 Meg box are a triffle (2.0 in
98). This is not entirely true: you can write pathological programs
where a single page means the difference between blinding speed and
hours swapping. Also the significant number is the increase in memory
you lack: a 500K deficit becoming 1 Meg. Consider also disk
bandwidth: being 16 megs short on a 32 Megs is much worse than 4 Meg
box on a 8 Meg because you need much more time to push 16 Megs to the
disk. On the other hand proceses will have to spend more time
analyzing a big array on a big box than a small one in a small box
(processor speed being equal) and this plays in the side of the 32
Megs being 16 Megs short for normal, non pathological programs.
Finally there is the question of probability: 500K is under 2% on a 32
Meg box so there is a good chance that when programs need more memory
than what you have they miss the mark by 20 or 30% and rarely fall
just straight on the 500K zone.
Needs refining but indulge with the fact I am writing at 2am.
A (not to be published) conclusion is: "Kernel compiling is a thing
performed only by idiots and kernel hackers". I am not a kernel
hacker and I have performed over 2 hundred of them. :-)
Perhaps we could help one another for our docs/articles.
--
Jean Francois Martinez
Project Independence: Linux for the Masses
http://www.independence.seul.org
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-11-20 6:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-19 0:20 jfm2
1998-11-19 20:05 ` Rik van Riel
1998-11-20 1:25 ` jfm2 [this message]
1998-11-20 15:31 ` Eric W. Biederman
1998-11-23 18:08 ` Stephen C. Tweedie
1998-11-23 20:45 ` jfm2
1998-11-23 21:59 ` jfm2
1998-11-24 1:21 ` Vladimir Dergachev
1998-11-24 11:17 ` Stephen C. Tweedie
1998-11-24 21:44 ` jfm2
1998-11-25 6:41 ` Rik van Riel
1998-11-25 12:27 ` Stephen C. Tweedie
1998-11-25 13:08 ` Rik van Riel
1998-11-25 14:46 ` Stephen C. Tweedie
1998-11-25 16:47 ` Rik van Riel
1998-11-25 21:02 ` Stephen C. Tweedie
1998-11-25 21:21 ` Rik van Riel
1998-11-25 22:29 ` Stephen C. Tweedie
1998-11-26 7:30 ` Rik van Riel
1998-11-26 12:48 ` Stephen C. Tweedie
1998-11-25 20:01 ` jfm2
1998-11-26 7:16 ` Rik van Riel
1998-11-26 19:59 ` jfm2
1998-11-27 17:45 ` Stephen C. Tweedie
1998-11-27 21:14 ` jfm2
1998-11-25 14:48 ` Eric W. Biederman
1998-11-25 20:29 ` jfm2
1998-11-25 16:31 ` ralf
1998-11-26 12:18 ` Rik van Riel
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=19981120012524.5136.qmail@sidney.remcomp.fr \
--to=jfm2@club-internet.fr \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=linux-mm@kvack.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