One of the things I find anoying about minix is having multiple compilers (just bcc and gcc). Just using one compiler (gcc in linux) really helps adhere to the KISS principle. But as Robert Blum points out, gcc is a hog. I guess this is why we see the 1.7 Meg buffer caches. While paging might be nice, you still have to reload gcc N times to compile an N module program, for the typical makefile. The only other way I see around the huge buffer cache is to implement the sticky bit to keep a programs pages in memory. The other alternative, #ifdef GCC, #ifdef C386 etc throughout the code, and having multiple object file types about, is even less savory. I would rather live with setting and clearing sticky bits before and after heavy compile sessions. I wonder what others think though?
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tejun Heo | [PATCH 2/5] sysfs: simplify sysfs_rename_dir() |
| Andi Kleen | [PATCH x86] [0/16] Various i386/x86-64 changes |
| Dave Hansen | Re: [RFC/PATCH] Documentation of kernel messages |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Thomas Gleixner | Re: [BUG] New Kernel Bugs |
