From: Zlatko Calusic <Zlatko.Calusic@CARNet.hr>
To: "Eric W. Biederman" <ebiederm+eric@ccr.net>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-mm@kvack.org
Subject: Re: Alpha quality write out daemon
Date: 20 Jan 1999 19:46:57 +0100 [thread overview]
Message-ID: <87hftllr32.fsf@atlas.CARNet.hr> (raw)
In-Reply-To: ebiederm+eric@ccr.net's message of "20 Jan 1999 08:52:33 -0600"
ebiederm+eric@ccr.net (Eric W. Biederman) writes:
[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.
>
Ha, ha. That comment reminded me of the times when I tried to walk all
of the page tables in a single call to swapout. I knew it wouldn't
work well, nor I was sure I'll be able to write such a code and have a
working system, but...
It actually worked, only the system got so DOG SLOW, I couldn't
believe. :)
In fact that's all I wanted to know, how much time is needed to scan
the page tables, so I could compare that to setup we use now (and some
imaginary logic I'll write one day in this or the next century :)).
And, of course, I wanted to learn few new bits and pieces of MM
internals, while writing the code.
For those mathematically challenged, whenever system got into memory
squeeze (almost all the time), it started spending 95% - 99% of CPU,
and swapout speed was few tens (at max) of KB's per second. :)
[snip]
> p.s.
> Since I'm getting some interest, here is my patch with all known
> bugs fixed. It doesn't work well but it isn't broken.
>
I very much appreciate people sending new code/patches. It is
interesting for testing or sometimes simply looking and meditating on
other people's ideas, so go ahead and send your patches, you're
welcome.
Unfortunately, I haven't tested your previous patch, only because I
was in the middle of testing my swaplock removal impact. Other MM
changes would have introduced a new variable in the testing, and I
wanted to avoid that.
But, I'm surely going to test your patch in some time.
Regards,
--
Zlatko
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1999-01-20 18:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-14 10:08 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 [this message]
1999-01-25 1:40 ` Eric W. Biederman
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=87hftllr32.fsf@atlas.CARNet.hr \
--to=zlatko.calusic@carnet.hr \
--cc=ebiederm+eric@ccr.net \
--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