From: Nir Livni <nirl@cyber-ark.com>
To: linux-kernel@vger.kernel.org
Subject: RE: shared objects, ELFs and memory usage
Date: Thu, 08 May 2003 13:43:14 +0300 [thread overview]
Message-ID: <E1298E981AEAD311A98D0000E89F45134B55FD@ORCA> (raw)
OK.
Thanks,
I am beginning to see the full picture now.
But I guess I am still missing something.
In the following "top" output,
Mem: 512396K av, 509208K used, 3188K free, 0K shrd, 10248K
buff
Swap: 522072K av, 0K used, 522072K free 417244K
cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
1538 unt033 9 0 4528 4524 4128 S 8.9 0.8 0:04
1596 unt006 16 0 4540 4536 4132 S 3.1 0.8 0:04
1509 unt004 11 0 4528 4524 4128 S 2.9 0.8 0:03
I understand that about 4MB from each process is shared using copy_on_write.
What does the "cached" portion of the output means ?
I see that almost all the "used" memory is also "cached".
(please CC me)
Thanks,
Nir
>
>
> On Thu, May 08, 2003 at 12:54:23PM +0300, Nir Livni wrote:
> > After compiling and linking my .so with the -shared option, I've
> > inspected strace output. I can clearly see that the shared object
> > (which is 2MB size) is NOT being
> > shared:
> > 1395 open("/usr/local/sharedclient.so", O_RDONLY) = 6
> > 1395 read(6,
> > "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340\200"...,
> > 1024) = 1024
> > 1395 fstat64(6, {st_mode=S_IFREG|0644, st_size=2079700, ...}) = 0
> > 1395 old_mmap(NULL, 2118824, PROT_READ|PROT_EXEC,
> MAP_PRIVATE, 6, 0) =
> > 0x401ea000
> > Any idea why ?
> > (Please CC me because I am not subscribed)
>
> It's called copy-on-write sharing. It is shared with the
> proviso that all modified pages are privatized and not
> committed to disk.
>
>
> -- wli
>
next reply other threads:[~2003-05-08 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 10:43 Nir Livni [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 9:54 Nir Livni
2003-05-08 10:01 ` William Lee Irwin III
2003-05-06 14:26 Nir Livni
2003-05-06 13:50 ` Richard B. Johnson
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=E1298E981AEAD311A98D0000E89F45134B55FD@ORCA \
--to=nirl@cyber-ark.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
all inboxes | Powered by JetHome®