public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin.Knoblauch" <Martin.Knoblauch@TeraPort.de>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Size of /proc/kcore growing over time ?
Date: Fri, 11 May 2001 15:14:39 +0200	[thread overview]
Message-ID: <3AFBE5BF.5865B0CA@TeraPort.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

Hi,

 is it normal that the size of /proc/kcore grows over time? Directly
after a boot it has the size of the physical memory. Over time it seems
to grow slightly. In about a day it went from 192 MB to about 203 MB.
This is 2.4.4-ac6 running on a Toshiba Notebook.

 I ask, because I thought the size of kproc could be used to determine
the amount of physical memory. If this assumption is wrong, is there
another way to achive the goal?

Happy weekend
Martin
-- 
------------------------------------------------------------------
Martin Knoblauch         |    email:  Martin.Knoblauch@TeraPort.de
TeraPort GmbH            |    Phone:  +49-89-510857-309
IT Services              |    Fax:    +49-89-510857-111
http://www.teraport.de   |    Mobile: +49-170-4904759

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Card for Martin.Knoblauch --]
[-- Type: text/x-vcard; charset=us-ascii; name="Martin.Knoblauch.vcf", Size: 381 bytes --]

begin:vcard 
n:Knoblauch;Martin
tel;cell:+49-170-4904759
tel;fax:+49-89-510857-111
tel;work:+49-89-510857-309
x-mozilla-html:FALSE
url:http://www.teraport.de
org:TeraPort GmbH;IT-Services
adr:;;Garmischer Straße 4;München;Bayern;D-80339;Germany
version:2.1
email;internet:Martin.Knoblauch@TeraPort.de
title:Senior System Engineer
x-mozilla-cpt:;32160
fn:Martin Knoblauch
end:vcard

             reply	other threads:[~2001-05-11 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 13:14 Martin.Knoblauch [this message]
2001-05-11 22:35 ` Size of /proc/kcore growing over time ? J . A . Magallon
2001-05-14  6:37   ` Martin.Knoblauch

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=3AFBE5BF.5865B0CA@TeraPort.de \
    --to=martin.knoblauch@teraport.de \
    --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