Hello from Gregg C Levine normally with Jedi Knight Computers As most of you have figured out, I happen to be fan of that series of films. All of them. So facts those are recounted in my signature, and taglines. But I've noticed that, for example John Campbell here, presents one, that is unfamiliar to me. So, the question is, "What are CLAIM Codes?" An answer is appreciated, but not necessary. Directly to me, so as to not clog up the list. ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )
> -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of > John Campbell > Sent: Thursday, April 25, 2002 5:34 PM > To: [EMAIL PROTECTED] > Subject: Re: LinuxWorld Article series - bufferring etc... > > John Summerfield: > >>>>>>>>>>>>> > > I try to maintain some recognition of weaknesses (no one system is > > ever good at _everything_). Working w/ Xenix (and Unix, early on) > > one of the tunables was to set the buffer cache size. While the > new > > model of buffer cache management is wonderful for "regular" (non- > > shared) systems, it's not as good in the VM environment (though we > > wouldn't want to cripple this feature across the s/390 line, since > > this feature is not a problem for the bare metal or an LPAR). > > I did mean to comment on this too;-) > > Linux's caching for single-OS machines isn't so wonderful either. I'm run a > postgresql database load a few times by way of a benchmark/test, and a > result is > that my 256 Mbytes of RAM gets absolutely full of database stuff. > > Then my desktop (KDE or GNOME) gets very slow indeed for a while until the > cache > gets recharged with stuff from /usr. > <<<<<<<<<<<<<<< > > But the /usr stuff that gets re-loaded are executables and data > (impure) > segments of the code to be run. Unless the KDE stuff is all > scripting > (yeah, like it's all done w/ tcl/TK, smoke and mirrors) then it's > going > to consist of computational pages rather than persistent storage > (which > is just a fancy AIX name for data that's reflected on disk; the code > segment of an executable gets to be both, in a way). > > It can be argued that the memory allocation mechanism needs to be > looked > at to allow a memory request to have it's own priority level, just > like > each process has a priority within the scheduler. Hmmmm... > > Doing this would benefit _all_ platforms. > > -------------------- > John R. Campbell, Speaker to Machines (GNUrd) {813-356|697}-5322 > "Will Work for CLAIM Codes" > IBM Certified: IBM AIX 4.3 System Administration, System Support
