From: Mike Fedyk <mfedyk@matchmail.com>
To: Robert Love <rml@tech9.net>
Cc: Mart?n Marqu?s <martin@bugs.unl.edu.ar>,
Marc Brekoo <kernel@brekoo.no-ip.com>,
linux-kernel@vger.kernel.org
Subject: Re: howto see shmem
Date: Wed, 24 Oct 2001 16:48:37 -0700 [thread overview]
Message-ID: <20011024164837.B22668@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011024214017.E5B1D2AB49@bugs.unl.edu.ar> <005001c15ce2$1123aec0$0500a8c0@brekoo.noip.com> <20011024232744.F14D62AB49@bugs.unl.edu.ar> <1003966646.3520.110.camel@phantasy>
In-Reply-To: <1003966646.3520.110.camel@phantasy>
On Wed, Oct 24, 2001 at 07:37:26PM -0400, Robert Love wrote:
> On Wed, 2001-10-24 at 19:27, Mart?n Marqu?s wrote:
> > [...]
> > ------ Shared Memory Segments --------
> > key shmid owner perms bytes nattch status
> > 0x00000000 65536 nobody 600 46084 11 dest
> > [...]
> > I can see 46084 bytes in shared memory used by the apache.
> > Am I wrong?
>
> Nope. Applications know how much the are sharing because they can
> easily see what region of memory is shared/mapped into their's.
>
> The reason the kernel can't figure out the net shared memory is because
> there is no simple way -- it has to add up the shared regions of all
> applications, counting each shared segment only once. Too much work.
>
Actually, if it's done in the COW code, you could quite possibly get most of
it right there...
Does anyone know of something that can make use of the shmem accting?
next prev parent reply other threads:[~2001-10-24 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 21:40 howto see shmem Martín Marqués
2001-10-24 23:17 ` Marc Brekoo
2001-10-24 23:27 ` Martín Marqués
2001-10-24 23:37 ` Robert Love
2001-10-24 23:39 ` Martín Marqués
2001-10-24 23:48 ` Mike Fedyk [this message]
2001-10-25 13:34 ` Christoph Rohland
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=20011024164837.B22668@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=kernel@brekoo.no-ip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@bugs.unl.edu.ar \
--cc=rml@tech9.net \
/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