From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrea Arcangeli <andrea@e-mind.com>
Cc: Zlatko Calusic <Zlatko.Calusic@CARNet.hr>,
"Eric W. Biederman" <ebiederm+eric@ccr.net>,
Linux-MM List <linux-mm@kvack.org>,
Linux Kernel List <linux-kernel@vger.rutgers.edu>
Subject: Re: Removing swap lockmap...
Date: Wed, 20 Jan 1999 17:09:47 GMT [thread overview]
Message-ID: <199901201709.RAA11707@dax.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990119191333.900A-100000@laser.bogus>
Hi,
On Tue, 19 Jan 1999 19:15:51 +0100 (CET), Andrea Arcangeli
<andrea@e-mind.com> said:
> On 19 Jan 1999, Zlatko Calusic wrote:
>> Yes, this case probably doesn't get enough testing with my current
>> setup, so it is quite hard (for me) to prove removing lockmap is
>> no-no. Problem is that I don't understand shm swapping very well
> Launch some time this proggy to try out shm swapping:
I have a shared memory stresser anyway if you want. However, when we
originally took out the lock map, it proved _very_ hard to reproduce the
race, and only a couple of people reported problems. Plain stress
testing with random access patterns over a day or more did not show up
the problem.
These races can be very nasty and hard to trigger. You really do need
to think the change through rather than just try-it-and-see.
--Stephen
--
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 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-18 15:12 Removing swap lockmap Zlatko Calusic
1999-01-18 20:26 ` Andrea Arcangeli
1999-01-18 22:24 ` BUG: deadlock in swap lockmap handling Alan Cox
1999-01-18 21:46 ` Removing swap lockmap Stephen C. Tweedie
1999-01-19 1:33 ` Zlatko Calusic
1999-01-19 0:34 ` Eric W. Biederman
1999-01-19 1:37 ` Zlatko Calusic
1999-01-19 18:15 ` Andrea Arcangeli
1999-01-20 17:09 ` Stephen C. Tweedie [this message]
1999-01-20 18:14 ` Zlatko Calusic
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=199901201709.RAA11707@dax.scot.redhat.com \
--to=sct@redhat.com \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=andrea@e-mind.com \
--cc=ebiederm+eric@ccr.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.