9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] python and lua
Date: Mon,  8 Jan 2001 14:26:53 +0900	[thread overview]
Message-ID: <20010108052708.3551D19A04@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

>Try running a few instances of the following program
>
>	for(i in `{seq 10})
>		memeat -x 10000000

I tried this on our dual pentium(133MHz) without local disk jus now.

swap area (/n/gabbroother/swap/trachyte) grew up to 40MB, and I
stopped the program at that point.  Nothing bad happened.
I'll not try it on my notebook with local disk, because I know what
happenes.  :-)

Kenji


[-- Attachment #2: Type: message/rfc822, Size: 2769 bytes --]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] python and lua
Date: Sun, 7 Jan 2001 23:12:50 -0500
Message-ID: <20010108041308.3BCC3199D7@mail.cse.psu.edu>

> What kind of situations?
> I asked this because I've never seen it.

Usually a terminal booted from local disk
can't sustain more than a few minutes of local disk swapping
before the window system or kfs swaps in a bogus page
and dies.  

Try running a few instances of the following program

	for(i in `{seq 10})
		memeat -x 10000000

and sit back.  This doesn't seem to happen when swapping
to a network file server.  Perhaps the timing is different.

I suspect something in the x86 memory management code,
although presotto says the carreras had similar problems.
I spent a day this summer trying to find anything, but
like everyone else came up empty handed.  

Instead, I moved more memory in from another machine
and turned off swapping.  On a laptop, of course,
this is less of an option, but I don't run my laptop
with swapping enabled either.  I'd much rather see 
"no physical memory" and type ^t^t k.

Russ


g% cat memeat.c
#include <u.h>
#include <libc.h>

void
main(int argc, char **argv)
{
	int xflag=0;
	int i, n;
	char *p;

	ARGBEGIN{
	case 'x':
		xflag=1;
	}ARGEND;
	n = atoi(argv[0]);
	p = malloc(n);
	memset(p, 0, n);
	i=0;
	for(;;) {
		sleep(1000+1000*(rand()%8));
		if(xflag)	memset(p, i++, n);
	}
}
g%

             reply	other threads:[~2001-01-08  5:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08  5:26 okamoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08  4:51 okamoto
2001-01-08  4:12 Russ Cox
2001-01-08  4:02 okamoto
2001-01-05 12:37 forsyth
2001-01-05 11:58 forsyth
2001-01-05  7:16 okamoto
2001-01-05  7:10 okamoto
2001-01-05  4:32 okamoto
2001-01-05  4:17 rob pike
2001-01-05  3:44 okamoto
2001-01-05  3:31 rob pike
2001-01-05  1:48 rob pike
2001-01-02 17:39 [9fans] A Plan 9 Python Interest Group? Randolph Fritz
2001-01-05  3:39 ` [9fans] python and lua Quinn Dunkan
2001-01-05  2:50   ` arisawa

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=20010108052708.3551D19A04@mail.cse.psu.edu \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --cc=9fans@cse.psu.edu \
    /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).