[CentOS] Swap: typical rehash. Why?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



I can't resist. Read the thread that was pointed to on lkml. ROTFLMAO.

*Real* UNIX addressed these problems long ago. I guess the "Gurus"
suffer from NIH (Not Invented Here) syndrome.

Given a "general purpose" system, tunability is a must. UNIX, as
delivered by USL in such examples as Sys V, had tunables that let admins
tune to their needs. A single "swappiness" value is woefully inadequate.

Among the tunables were how much memory for cache, how much for buffers,
how much for X/Y/Z, high and low water marks for all sorts of memory
related stuff and a very valuable attribute bit for executables called
the "sticky bit". It is not the "sticky bit" as used now. It said lock
this app in memory and never swap it. A variation on that (couldn't keep
original semantics with the size of apps these days) would address some
of the "responsiveness" issues raised by some. Some admin tunables would
address the other issues.

The "Gurus" need to learn something my father taught me. "A smart man
learns from his mistakes. A wise man learns from the mistakes of
others". I'm really smart. :-(  And, apparently, so are the "Gurus". To
think they have VM this long and no one has thought to swipe these good
ideas from real UNIX. And they're still argueing about all that as if it
has never been hashed out and addressed before.

-- 
Bill

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux