From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: Zlatko.Calusic@CARNet.hr
Cc: "Eric W. Biederman" <ebiederm+eric@ccr.net>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-mm@kvack.org
Subject: Re: Alpha quality write out daemon
Date: 24 Jan 1999 19:40:23 -0600 [thread overview]
Message-ID: <m1ww2cuo3c.fsf@flinx.ccr.net> (raw)
In-Reply-To: Zlatko Calusic's message of "20 Jan 1999 19:46:57 +0100"
>>>>> "ZC" == Zlatko Calusic <Zlatko.Calusic@CARNet.hr> writes:
ZC> ebiederm+eric@ccr.net (Eric W. Biederman) writes:
ZC> [snip]
>>
>> 2) You can walk the page tables very fast.
>> Not fast enough to want to walk all of the pages for a single call of try to free pages.
>> But fast enough to refill the dirty list.
>>
ZC> Ha, ha. That comment reminded me of the times when I tried to walk all
ZC> of the page tables in a single call to swapout. I knew it wouldn't
ZC> work well, nor I was sure I'll be able to write such a code and have a
ZC> working system, but...
ZC> It actually worked, only the system got so DOG SLOW, I couldn't
ZC> believe. :)
ZC> In fact that's all I wanted to know, how much time is needed to scan
ZC> the page tables, so I could compare that to setup we use now (and some
ZC> imaginary logic I'll write one day in this or the next century :)).
ZC> And, of course, I wanted to learn few new bits and pieces of MM
ZC> internals, while writing the code.
ZC> For those mathematically challenged, whenever system got into memory
ZC> squeeze (almost all the time), it started spending 95% - 99% of CPU,
ZC> and swapout speed was few tens (at max) of KB's per second. :)
Well this actually comes much closer to my experience than I like.
My first mistake was to trust the times on the syslog entry as something
reasonbly close to the truth. Nope.
After I put jiffy counters on my debug messages the results I got changed noticeably.
In particular. Normally a page table scan is just a couple of jiffies.
But occasionally when I had a lot of dirty pages (16M out of 32M), I was having page table scans
take about 15 seconds per scan.
It may just be that my logic per page table entry was just too expensive.
I'm going to investigate that, and with luck that will be the case,
otherwise I'm going to start seriously considering reverse page table entries.
Eric
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-01-25 3:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-14 10:08 Alpha quality write out daemon Eric W. Biederman
[not found] ` <369E0501.987D2B3B@xinit.se>
1999-01-14 16:49 ` Eric W. Biederman
1999-01-15 7:31 ` Eric W. Biederman
1998-01-14 18:44 ` Hans Eric Sandström
1999-01-15 9:02 ` Eric W. Biederman
1999-01-17 6:12 ` Beta " Eric W. Biederman
1999-01-18 5:05 ` Eric W. Biederman
1999-01-19 15:15 ` Alpha " Stephen C. Tweedie
1999-01-20 14:52 ` Eric W. Biederman
1999-01-20 18:46 ` Zlatko Calusic
1999-01-25 1:40 ` Eric W. Biederman [this message]
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=m1ww2cuo3c.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
/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