From: Zlatko Calusic <Zlatko.Calusic@CARNet.hr>
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
Benjamin Redelings I <bredelin@ucsd.edu>,
Linux Kernel <linux-kernel@vger.rutgers.edu>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [2.1.130-3] Page cache DEFINATELY too persistant... feature?
Date: 30 Nov 1998 23:27:07 +0100 [thread overview]
Message-ID: <87sof0ke9w.fsf@atlas.CARNet.hr> (raw)
In-Reply-To: Rik van Riel's message of "Mon, 30 Nov 1998 20:29:35 +0100 (CET)"
Rik van Riel <H.H.vanRiel@phys.uu.nl> writes:
> I am now trying:
> if (buffer_over_borrow() || pgcache_over_borrow() ||
> atomic_read(&nr_async_pages)
> shrink_mmap(i, gfp_mask);
>
> Note that this doesn't stop kswapd from swapping out so
> swapout performance shouldn't suffer. It does however
> free up memory so kswapd should _terminate_ and keep the
> amount of I/O done to a sane level.
This still slows down swapping somewhat (20-30%) in my tests.
>
> Note that I'm running with my experimentas swapin readahead
> patch enabled so the system should be stressed even more
> than normally :)
>
I tried your swapin_readahead patch but it didn't work right:
swap_duplicate at c012054b: entry 00011904, unused page
swap_duplicate at c012054b: entry 002c8c00, unused page
swap_duplicate at c012054b: entry 00356700, unused page
swap_duplicate at c012054b: entry 00370f00, unused page
swap_duplicate at c012054b: entry 0038d000, unused page
swap_duplicate at c012054b: entry 0039d100, unused page
swap_duplicate at c012054b: entry 0000b500, unused page
c012054b is read_swap_cache_async()
Memory gets eaten when I bang MM, and after sometime system blocks. I
also had one FS corruption, thanks to that. Didn't investigate
further.
Do you have a newer version of the patch?
Regards,
--
Posted by Zlatko Calusic E-mail: <Zlatko.Calusic@CARNet.hr>
---------------------------------------------------------------------
Multitasking attempted. System confused.
--
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:[~1998-11-30 22:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199811261236.MAA14785@dax.scot.redhat.com>
[not found] ` <Pine.LNX.3.95.981126094159.5186D-100000@penguin.transmeta.com>
1998-11-27 16:02 ` Stephen C. Tweedie
1998-11-27 17:19 ` Chip Salzenberg
1998-11-27 18:31 ` Linus Torvalds
1998-11-27 19:58 ` Zlatko Calusic
1998-11-30 11:15 ` Stephen C. Tweedie
1998-11-30 23:13 ` Zlatko Calusic
1998-11-30 12:37 ` Rik van Riel
1998-11-30 15:12 ` Zlatko Calusic
1998-11-30 19:29 ` Rik van Riel
1998-11-30 22:27 ` Zlatko Calusic [this message]
1998-11-30 23:11 ` Rik van Riel
1998-11-30 20:20 ` Andrea Arcangeli
1998-11-30 22:28 ` Zlatko Calusic
1998-11-28 7:31 ` Eric W. Biederman
1998-11-30 11:13 ` Stephen C. Tweedie
1998-11-30 15:08 ` Rik van Riel
1998-11-30 21:40 ` Eric W. Biederman
1998-11-30 22:00 ` 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=87sof0ke9w.fsf@atlas.CARNet.hr \
--to=zlatko.calusic@carnet.hr \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=bredelin@ucsd.edu \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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