From: Andrea Arcangeli <andrea@e-mind.com>
To: Zlatko Calusic <Zlatko.Calusic@CARNet.hr>
Cc: "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: Tue, 19 Jan 1999 19:15:51 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.3.96.990119191333.900A-100000@laser.bogus> (raw)
In-Reply-To: <871zksqbyq.fsf@atlas.CARNet.hr>
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:
/*
* Copyright (C) 1999 Andrea Arcangeli
* shm swapout test
*/
#include <sys/ipc.h>
#include <sys/shm.h>
#define SIZE 16000000
main()
{
int shmid;
char *addr, *p;
if ((shmid = shmget(IPC_PRIVATE, SIZE, IPC_CREAT | 0644)) < 0)
perror("shmget");
if ((addr = shmat(shmid, NULL, 0)) < 0)
perror("shmat");
for (p = addr; p < addr + SIZE; p+=4096)
*p = 0;
}
To know if the lockmap is needed you can also reinsert the code and add a
printk() in the test_and_set_bit() path.
Andrea Arcangeli
--
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 2:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-18 15:12 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 [this message]
1999-01-20 17:09 ` Stephen C. Tweedie
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=Pine.LNX.3.96.990119191333.900A-100000@laser.bogus \
--to=andrea@e-mind.com \
--cc=Zlatko.Calusic@CARNet.hr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox