linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Zheng, Jeff" <jeff.zheng@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is it a bug (about share memory)?
Date: Sun, 24 Aug 2003 02:48:41 -0700	[thread overview]
Message-ID: <20030824024841.7c641454.akpm@osdl.org> (raw)
In-Reply-To: <37FBBA5F3A361C41AB7CE44558C3448E011958E9@pdsmsx403.ccr.corp.intel.com>

"Zheng, Jeff" <jeff.zheng@intel.com> wrote:
>
> I tried to use share memory to check vm overcommit by check Committed_AS
> in /proc/meminfo. It seems that attach of share momory will add the value
> of Committed_AS but detach of share memory does not reduce the value of
> Committed_AS.

shmdt() will not release resources.  Run `ipcs' after your test app and you
will see the shm segment is still there.

Release it with ipcrm and Committed_AS falls back as expected.


      reply	other threads:[~2003-08-24  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22  8:15 Is it a bug (about share memory)? Zheng, Jeff
2003-08-24  9:48 ` Andrew Morton [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=20030824024841.7c641454.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jeff.zheng@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).