From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] more fun with many maches
Date: Fri, 25 Jun 2010 23:24:11 -0400 [thread overview]
Message-ID: <104a5f0acfa2903a5f3e04503dcffcd2@kw.quanstro.net> (raw)
i added some tracing to tell me who's allocating what when
and on what mach.
a little mistake in the summary was very interesting.
instead of printing the number of fast frees per mach,
the total number of frees per procssor was printed.
the imbalance is surprising:
128 [20/100/10] block size
share 0/100 nslow 103444 nsfree 10350
nmalloc 103434 nfree 103400
0 0/0 nfast 10972 nffree 10982
1 1/1 nfast 11676 nffree 11747
2 0/0 nfast 11695 nffree 11725
3 2/2 nfast 11427 nffree 11429
>> 4 28/28 nfast 22778 nffree 126046
5 0/0 nfast 5134 nffree 5114
6 0/0 nfast 11743 nffree 11773
7 0/0 nfast 11945 nffree 11985
tot 31 nfast 97370 nffree 200801
seems almost all the allocation takes place on mach 4.
this is consistent across reboot. why?
- erik
reply other threads:[~2010-06-26 3:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=104a5f0acfa2903a5f3e04503dcffcd2@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).