Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]RE: memory holes and kernel params
- To: "'tlug@example.com'" <tlug@example.com>
- Subject: RE: memory holes and kernel params
- From: "Doughty, Michael" <Doughty_Michael@example.com>
- Date: Fri, 27 Jul 2001 19:51:18 +0900
- Delivered-To: tlug@example.com
- List-Help: <mailto:tlug-request@example.comsubject=help>
- List-Post: <mailto:tlug@example.com>
- List-Subscribe: <mailto:tlug-request@example.comsubject=subscribe>
- List-Unsubscribe: <mailto:tlug-request@example.comsubject=unsubscribe>
- Old-Return-Path: <Doughty_Michael@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <IrjwN.A.GLD.jfUY7@example.com>
- Resent-Sender: tlug-request@example.com
In case anyone cares, the answer (found via the careful and exact science of trial and error) is as follows: The statement mem=###M@example.com means that there is a contiguous of ###MB Ram starting at the 16M point. This means that if you have 128M of ram, the statement to use all of it after the 16M hole would be: mem=112M@example.com But wait! There's more!! If you want to use it all, the following statement is great: mem=exactmap mem=14M@example.com mem=112M@example.com This nets me a total of 126 megs. I could probably get a little more if I chose to start at the 0 or 640k mark, but as some machines appear to have a hole at both 0 and 15M, I decided to be on the extra cautious side. Anyone want to throw out an improvement on this approach of mine? Michael -----Original Message----- From: Doughty, Michael Sent: 13”N7ŒŽ26“ú 19:06 To: 'tlug@example.com' Subject: memory holes and kernel params Ok, here is the deal. I have an ancient Compaq 1500 beast that I have dropped linux on. But I have a minor problem, in that it has a memory hole that is causing the kernel a bit of grief. Now I know I can warn it about the memory hole in lilo.conf with a line like: append="mem=##M@example.com" What I don't know, and can't find any documentation on, is what do the ## stand for? Does this line say I have a contiguous block of RAM that is ## in size starting at 16M, or does it say I have a total of ## in ram, with a 1MB hole running from 15M-16M? ie, if I have 128M of physical memory and a memory hole at 15-16M, should my lilo line look like: append="mem=112M@example.com" or append="mem=128M@example.com" Thanks, Michael ----------------------------------------------------------------------- Next Nomikai Meeting: Fri, Aug 10 19:30- Tengu Tokyo Eki-Mae Next Technical Meeting: Sat, Sep 15 13:30- Akasaka Kumin Center ----------------------------------------------------------------------- more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
Home | Main Index | Thread Index
- Prev by Date: Re: Kana/Kanji
- Next by Date: KDE Sound
- Prev by thread: memory holes and kernel params
- Next by thread: Kana/Kanji
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links