public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Christian Schmidt <lkml@digadd.de>, linux-kernel@vger.kernel.org
Subject: Re: Memory consumption on linux
Date: Wed, 2 May 2007 09:11:17 -0700	[thread overview]
Message-ID: <20070502161117.GW19966@holomorphy.com> (raw)
In-Reply-To: <p73odl3xvie.fsf@bingen.suse.de>

Christian Schmidt <lkml@digadd.de> writes:
>> Global cache is easy to understand - file system / inode caches. What
>> exactly is buffers, though?

On Wed, May 02, 2007 at 02:25:29PM +0200, Andi Kleen wrote:
> http://www.halobates.de/memorywaste.pdf and http://www.halobates.de/memory.pdf
> give some overview of in kernel memory users.

Very interesting. This is a veritable TODO list.


-- wli

      reply	other threads:[~2007-05-02 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 19:31 Memory consumption on linux Christian Schmidt
2007-05-01 21:00 ` Jan Knutar
2007-05-02 12:25 ` Andi Kleen
2007-05-02 16:11   ` William Lee Irwin III [this message]

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=20070502161117.GW19966@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@digadd.de \
    /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