mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Greg Bledsoe" <greg.bledsoe@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pmap, smap, process memory utilization
Date: Wed, 28 Jun 2006 10:55:17 -0500	[thread overview]
Message-ID: <dba10b900606280855g6d415441y92c46ca83c74a469@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0606280511320.32286@gandalf.stny.rr.com>

Thank you for your reply.

On 6/28/06, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Tue, 27 Jun 2006, Greg Bledsoe wrote:
>
> Even if this did work, it will not equal the free command. Since the
> buffers/cache may mix you up.  Some of the buffers can be allocated to
> files that are also mapped, not to mention, you need to account for
> slabs and memory allocated by drivers.
>
> -- Steve
>

Thank you.  This information is extremely difficult to find without
digging into kernel code, which I certainly wish I had time to do, but
don't, and particulars of how many aspects of memory management happen
seems to be nonexistant.  I would like to document this aspect, at
least, as well as I am able and post somewhere to add to the worlds'
global knowledge pool on this subject, and prevent the lkml from
getting bugged about this anymore.

This leads me to the question though, of how the kernel keeps track of
this information overall to report accurately via free and vmstat.
Does it just keep an overall count on the fly as memory is allocated?
And, getting ahead of myself, if that can be done, is it just
considered too expensive to keep a similar acount for each proccess?
That seems to be what I am hearing in previous lkml discussions.

Also, since it seems virtually impossible to get this data on a
per-process basis, does smap suffer from these same difficulties, as
it seems to calculate this information when asked, and not keep it
from process start time.

Again, thank you for your time.

-- 
   Greg Bledsoe

    ----------
    I owe my success to having listened respectfully to the very best
advice, and going and doing the exact opposite.
    G.K. Chesterton

  reply	other threads:[~2006-06-28 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 18:40 Greg Bledsoe
2006-06-28  9:36 ` Steven Rostedt
2006-06-28 15:55   ` Greg Bledsoe [this message]
2006-06-29  6:34     ` Steven Rostedt
2006-06-29 17:46       ` Nick Piggin

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=dba10b900606280855g6d415441y92c46ca83c74a469@mail.gmail.com \
    --to=greg.bledsoe@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®