From: "Stephen C. Tweedie" <sct@redhat.com>
To: Chuck Lever <cel@monkey.org>
Cc: Andrea Arcangeli <andrea@e-mind.com>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: [PFC]: hash instrumentation
Date: Fri, 9 Apr 1999 11:44:03 +0100 (BST) [thread overview]
Message-ID: <14093.55795.868790.820299@dukat.scot.redhat.com> (raw)
In-Reply-To: <Pine.BSF.4.03.9904081311320.1995-100000@funky.monkey.org>
Hi,
On Thu, 8 Apr 1999 13:22:25 -0400 (EDT), Chuck Lever <cel@monkey.org>
said:
> i'm discovering that a 13 bit hash mitigates the spikey size distribution
> in the page hash *better* than the +offset change. although i've been
> able to push the system into swap, i still haven't seen any degenerate
> hash behavior that's as bad as the buffer cache's hash function.
Pushing it into swap is not sufficient: to trigger the swap cache you
need to be actively using data which has previously been swapped out,
which requires dirtying the pages, swapping them out and then touching
them again for read access. In that special case, when the
newly-swapped-back-in page still matches the copy on disk, the swap
cache mechanism keeps both the in-memory and on-disk copies linked to
each other.
> i'll have more as i test this further.
Don't forget that you can use the "mem=*m" option at boot time to run
in a reduced memory configuration. That might make it a bit easier
for you to trigger this stuff. :)
--Stephen
--
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/
parent reply other threads:[~1999-04-09 10:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.BSF.4.03.9904081311320.1995-100000@funky.monkey.org>]
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=14093.55795.868790.820299@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=andrea@e-mind.com \
--cc=cel@monkey.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.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