From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9front@9front.org
Subject: Re: [9front] 9pc64
Date: Fri, 2 May 2014 08:34:20 +0900 [thread overview]
Message-ID: <3B54C219-B268-4BAA-9638-62CEF6E18EDB@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <33b8b17a064a9166802d333f512a5ba7@felloff.net>
memory command on 9pc64
term% memory
total 15.9 GB
total kernel 2 GB
total user 13.9 GB
used user 8.32 MB
used kernel 11.6 MB
used draw 13.3 MB
term%
Test if large memory is really allocated to a process.
H2: Test Code
void
main(int argc, char *argv[])
{
char *p, buf[256];
ulong i,n[4];
ulong GB = 1024*1024*1024;
ARGBEGIN{
default: usage();
}ARGEND
n[0] = 1;
n[1] = 1;
n[2] = 1;
n[3] = 1;
for(i = 0; i< 4; i++){
p = malloc(n[i]*GB);
print("%d %dGB %08p\n",i,n[i],p);
}
read(0,buf, sizeof(buf));
}
H2: The Result
H3: 9front (9pc64)
term% 6.out
0 1GB 00401938
1 1GB 404019a0
2 1GB 80401a08
3 1GB 00000000
the 6.out is running
term% ps | grep 6.out
arisawa 1383 0:00 0:00 56K Pread 6.out
term% memory
total 15.9 GB
total kernel 2 GB
total user 13.9 GB
used user 8.28 MB
used kernel 10.5 MB
used draw 13.3 MB
term%
H3: 9front (9pcf)
term% 8.out
0 1GB 0000a4a0
1 1GB 00000000
2 1GB 00000000
3 1GB 00000000
the 8.out is running
term% ps |grep 8.out
arisawa 1843 0:00 0:00 48K Pread 8.out
term% memory
total 3.42 GB
total kernel 154 MB
total user 3.27 GB
used user 859 MB
used kernel 6.38 MB
used draw 8.77 MB
term%
Totally OK.
It would be better if we get total memory size allocated to a process.
memory command on both 9pcf and 9pc64 does not show malloced size.
On 2014/05/02, at 6:51, cinap_lenrek@felloff.net wrote:
> so it works?
>
> --
> cinap
next prev parent reply other threads:[~2014-05-01 23:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 4:25 9FRONT "опен-сссл" Released sl
2014-04-28 10:52 ` cwfs fsmempercent arisawa
2014-04-28 17:08 ` [9front] " cinap_lenrek
2014-04-28 17:26 ` cinap_lenrek
2014-04-28 22:55 ` arisawa
2014-04-29 20:11 ` cinap_lenrek
2014-04-30 14:41 ` Kenji Arisawa
2014-04-30 20:14 ` cinap_lenrek
2014-05-01 10:39 ` 9pc64 arisawa
2014-05-01 11:07 ` [9front] 9pc64 Aram Hăvărneanu
2014-05-01 14:06 ` arisawa
2014-05-01 14:25 ` cinap_lenrek
2014-05-01 14:39 ` cinap_lenrek
2014-05-01 15:27 ` cinap_lenrek
2014-05-01 21:49 ` Kenji Arisawa
2014-05-01 21:51 ` cinap_lenrek
2014-05-01 23:22 ` Kenji Arisawa
2014-05-01 23:34 ` Kenji Arisawa [this message]
2014-05-02 0:22 ` cinap_lenrek
2014-05-02 11:02 ` Aram Hăvărneanu
2014-05-04 5:24 ` malloc Kenji Arisawa
2014-05-04 8:22 ` [9front] malloc arisawa
2014-05-04 12:40 ` [9front] cwfs fsmempercent arisawa
2014-05-04 23:22 ` cinap_lenrek
2014-05-05 0:11 ` arisawa
2014-05-05 0:31 ` cinap_lenrek
2014-05-05 0:43 ` cinap_lenrek
2014-05-05 2:04 ` arisawa
2014-05-05 4:32 ` cinap_lenrek
2014-05-05 8:00 ` arisawa
2014-05-05 11:15 ` arisawa
2014-05-05 12:08 ` arisawa
2014-05-03 0:37 ` cinap_lenrek
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=3B54C219-B268-4BAA-9638-62CEF6E18EDB@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9front@9front.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).