From: Hal Martin <hal.martin@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] RAM upgrade, kernel and swap
Date: Wed, 23 Jan 2008 22:39:05 -0500 [thread overview]
Message-ID: <47980859.2050801@gmail.com> (raw)
In-Reply-To: <20080123131423.29edc59b@lbg2.evolone.org>
Ahh, but it won't last...
$ free
total used free shared
buffers cached
Mem: 2059824 2044512 15312 0 37636 50868
-/+ buffers/cache: 1956008 103816
Swap: 4289308 1229024 3060284
Now this I can live with...
$ free
total used free shared
buffers cached
Mem: 3629832 3499156 130676 0 56644 3070796
-/+ buffers/cache: 371716 3258116
Swap: 0 0 0
Unfortunately that machine is 32bit and thus only supports ~3.6GB of the
4GB of RAM. :-(
-Hal
Michael Higgins wrote:
> On Tue, 22 Jan 2008 00:44:53 +0100
> "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de> wrote:
>
>
>> On Montag, 21. Januar 2008, Michael Higgins wrote:
>>
>>> So, I just got 2 GB of RAM in the mail. Whoo hoo.
>>>
>>> Before I pop these in, soliciting any thoughts about the following:
>>>
>>> zcat /proc/config.gz |grep MEM
>>> CONFIG_SHMEM=y
>>> # CONFIG_TINY_SHMEM is not set
>>> # CONFIG_NOHIGHMEM is not set
>>> CONFIG_HIGHMEM4G=y
>>> # CONFIG_HIGHMEM64G is not set
>>> CONFIG_HIGHMEM=y
>>> CONFIG_SELECT_MEMORY_MODEL=y
>>> CONFIG_FLATMEM_MANUAL=y
>>> # CONFIG_DISCONTIGMEM_MANUAL is not set
>>> # CONFIG_SPARSEMEM_MANUAL is not set
>>> CONFIG_FLATMEM=y
>>> CONFIG_FLAT_NODE_MEM_MAP=y
>>> # CONFIG_SPARSEMEM_STATIC is not set
>>> CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
>>> # CONFIG_BLK_DEV_UMEM is not set
>>> # CONFIG_INPUT_FF_MEMLESS is not set
>>> # CONFIG_DEBUG_HIGHMEM is not set
>>> CONFIG_HAS_IOMEM=y
>>>
>>>
>>> Name Flags Part Type FS Type [Label]
>>> Size (MB)
>>> ---------------------------------------------------------------------------
>>> --- hda1 Boot Primary Linux ext2
>>> 256.50 hda2 Primary Linux swap /
>>> Solaris 1024.46 hda3 Primary Linux
>>> ext3 21480.44 hda5 Logical
>>> Linux ReiserFS 28771.84 hda6
>>> Logical Linux ReiserFS 28493.15
>>>
>>> IOW, do I need to/should I recompile my kernel or change partition
>>> sizes?
>>>
>> if you don't plan to try suspend-to-disk.
>> No
>>
>> even if you plan to try suspend-to-disk it might work with a
>> swapfile. So still no.
>>
>
> Thanks for the feedback. I figured I'd be covered with the setup as it
> is, but you never know... unless you know. This thing never sleeps...
> so no worries there.
>
> Anyway, I just popped 'em in:
>
> $ free
> total used free shared buffers cached
> Mem: 2074548 166048 1908500 0 6812 77284
> -/+ buffers/cache: 81952 1992596
> Swap: 1000432 0 1000432
>
> [ Nice. I like that last line a lot. ]
>
> Cheers,
>
>
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-24 3:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 21:42 [gentoo-user] RAM upgrade, kernel and swap Michael Higgins
2008-01-21 23:44 ` Hemmann, Volker Armin
2008-01-23 21:14 ` Michael Higgins
2008-01-24 3:39 ` Hal Martin [this message]
2008-01-24 9:55 ` Ricardo Saffi Marques
2008-01-24 12:56 ` Hemmann, Volker Armin
2008-01-24 13:01 ` Ricardo Saffi Marques
2008-01-24 14:19 ` Hemmann, Volker Armin
2008-01-24 14:23 ` Ricardo Saffi Marques
2008-01-24 14:41 ` Hal Martin
2008-01-24 14:42 ` Dirk Heinrichs
2008-01-24 15:07 ` Hemmann, Volker Armin
2008-01-24 15:16 ` Hemmann, Volker Armin
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=47980859.2050801@gmail.com \
--to=hal.martin@gmail.com \
--cc=gentoo-user@lists.gentoo.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