From: "Lee Revell" <rlrevell@joe-job.com>
To: "Rik van Riel" <riel@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: VM question - accounting of SysV SHM
Date: Wed, 17 Oct 2007 17:11:30 -0400 [thread overview]
Message-ID: <75b66ecd0710171411n55efdb5bt8e9627301ed9088e@mail.gmail.com> (raw)
In-Reply-To: <20071017165857.08b887e9@bree.surriel.com>
On 10/17/07, Rik van Riel <riel@redhat.com> wrote:
> On Wed, 17 Oct 2007 16:49:07 -0400
> "Lee Revell" <rlrevell@joe-job.com> wrote:
>
> > Sorry to ask this question on the list but I've Googled and found
> > nothing.
> >
> > Is system V shared memory accounted for as Cached, or as normal
> > application memory?
>
> Cached.
>
> Shared memory segments basically are tmpfs files.
Thanks!
Are there any plans to track it separately in a future kernel release?
I've also noticed that if huge pages are used for the shared memory,
they are not accounted for as cached - I have a 56GB huge page pool
but cached is only 6GB. Is this behavior specific to huge pages?
Finally, are these quirks documented anywhere?
Lee
prev parent reply other threads:[~2007-10-17 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 20:49 Lee Revell
2007-10-17 20:58 ` Rik van Riel
2007-10-17 21:11 ` Lee Revell [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=75b66ecd0710171411n55efdb5bt8e9627301ed9088e@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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®