From: "hv" <hv@trust-mart.com>
To: "Mike Turcotte" <Mike.Turcotte@cityofnorthbay.ca>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: memory size
Date: Thu, 24 Mar 2005 11:05:51 +0800 [thread overview]
Message-ID: <003001c5301e$63628400$d87f11ac@hv> (raw)
In-Reply-To: C6FD667B200BDF4F964C1BA77B796CE20F5E43@cnbmail2.city.north-bay.on.ca
There is another dell2650 with 2G memory using option "CONFIG_HIGHMEM4G":
Memory: 2075744k/2097024k available (1858k kernel code, 20408k reserved,
704k data, 160k init, 1179520k highmem)
2097024-1858-20408-704-160=2073894.It looks be close to 2075744. So I
consider it would be fine.
But when I use option "CONFIG_HIGHMEM64G" in these dell6650
Memory: 16116752k/16777216k available (1855k kernel code, 135136k reserved,
702k data, 164k init, 15335296k highmem)
16777216-1855-135136-702-164=16639359.
16639359 is far from 16116752.I think "The first 800 and sum odd MB of
memory" would be in the area (1855k kernel code, 135136k reserved, 702k
data, 164k init, 15335296k highmem).Is this right?
----- Original Message -----
From: "Mike Turcotte" <Mike.Turcotte@cityofnorthbay.ca>
To: "hv" <hv@trust-mart.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, March 24, 2005 12:57 AM
Subject: RE: memory size
The first 800 and sum odd MB of memory are not considered high memory,
so it will not appear in the output. By taking a quick look at your
numbers, it seems fine
Michael Turcotte
Information Systems
City of North Bay
200 McIntyre St. E
PO Box 360
North Bay, Ontario
P1B 8H8
Mike.Turcotte@cityofnorthbay.ca
http://www.cityofnorthbay.ca
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of hv
> Sent: Wednesday, March 23, 2005 3:09 AM
> To: hv
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: memory size
>
> The other dell6650 with 16G ram under kernel 2.6.11-rc4-mm1 is more
> oddness.
> Memory: 16116752k/16777216k available (1855k kernel code, 135136k
> reserved,
> 702k data, 164k init, 15335296k highmem)
>
>
> ----- Original Message -----
> From: "hv" <hv@trust-mart.com>
> To: <linux-kernel@vger.kernel.org>
> Sent: Wednesday, March 23, 2005 3:54 PM
> Subject: memory size
>
>
> > Hi,all:
> > This is my memory status from "dmesg":
> > Memory: 4673020k/5242880k available (1334k kernel code, 44532k
reserved,
> > 672k data, 156k init, 3800960k highmem)
> >
> >
> > But I found that available memory size is much less than physical
memory
> > size.My server is Dell6650 with P4 Xeon*4 and 5G Ram.
> > My kernel version is 2.6.12-rc1-mm1.Could any one tell my the
> > reason?Thanks.
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe
linux-kernel"
> in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
> >
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-03-24 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 16:57 memory size Mike Turcotte
2005-03-24 3:05 ` hv [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-23 7:54 hv
2005-03-23 8:09 ` hv
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='003001c5301e$63628400$d87f11ac@hv' \
--to=hv@trust-mart.com \
--cc=Mike.Turcotte@cityofnorthbay.ca \
--cc=linux-kernel@vger.kernel.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