From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrea Arcangeli <andrea@e-mind.com>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org,
"Stephen C. Tweedie" <sct@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: PG_clean for shared mapping smart syncing
Date: Sat, 19 Dec 1998 16:36:54 GMT [thread overview]
Message-ID: <199812191636.QAA01194@dax.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.981219171852.506A-100000@laser.bogus>
Hi,
On Sat, 19 Dec 1998 17:23:13 +0100 (CET), Andrea Arcangeli
<andrea@e-mind.com> said:
> I've put a new patch with as difference only a bit of credits added ;) at:
> ftp://e-mind.com/pub/linux/kernel-patches/pgclean-0-2.1.132-2.diff.gz
> All tests I done here are been succesfully (and I am using huge size of
> memory just to be sure to notice any kind of mm corruption). Does somebody
> has some test suite for shared mappings or could suggest me a proggy that
> uses heavly shared mappings?
ftp.uk.linux.org:/pub/linux/sct/vm/shm-stress.tar.gz
It currently uses only sysV shared maps, but it would be trivial to
extend it to use shared map files. Let me know if you make the change
and I'll merge the patch in.
The test stuff uses separate shared-write regions for testing: one
smaller region is used as a bitmap, and the code keeps primitive
spinlocks in this bit to synchronise access to the rest of the shared
memory. The rest of the shared memory is used as a test heap --- just a
collection of separate test pages --- and a pattern array. We store
random patterns in the first word of each test page in the heap, and
(under spinlock) assign the same pattern atomically to both the test
page and the appropriate entry in the pattern array. Use a sufficiently
large test heap and you can test shared-page swapping quite effectively.
--Stephen
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
prev parent reply other threads:[~1998-12-19 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-19 16:04 Andrea Arcangeli
1998-12-19 16:17 ` Stephen C. Tweedie
1998-12-19 16:27 ` Andrea Arcangeli
1998-12-19 16:37 ` Andrea Arcangeli
1998-12-19 16:46 ` Andrea Arcangeli
1998-12-19 17:10 ` Stephen C. Tweedie
1998-12-19 16:23 ` Andrea Arcangeli
1998-12-19 16:36 ` Stephen C. Tweedie [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=199812191636.QAA01194@dax.scot.redhat.com \
--to=sct@redhat.com \
--cc=andrea@e-mind.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--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