From: Rik van Riel <riel@conectiva.com.br>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: sct@conectiva.com.br, linux-kernel@conectiva.com.br
Subject: Re: changing mm->mmap_sem (was: Re: system call for process information?)
Date: Sun, 18 Mar 2001 11:43:48 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0103181122480.13050-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.33.0103181407520.1426-100000@mikeg.weiden.de>
On Sun, 18 Mar 2001, Mike Galbraith wrote:
> > No, this was make -j30 bzImage. (nscd was running though...)
>
> I rebooted, shut down nscd prior to testing and did 5 builds in a row
> without a single gripe. Started nscd for sixth run and instantly the
> kernel griped. Yup.. threaded apps pushing swap.
OK, I'll write some code to prevent multiple threads from
stepping all over each other when they pagefault at the
same address.
What would be the preferred method of fixing this ?
- fixing do_swap_page and all ->nopage functions
- hacking handle_mm_fault to make sure no overlapping
pagefaults will be served at the same time
regards,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com.br/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next parent reply other threads:[~2001-03-18 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0103181407520.1426-100000@mikeg.weiden.de>
2001-03-18 14:43 ` Rik van Riel [this message]
[not found] <Pine.LNX.4.33.0103141618320.21132-100000@duckman.distro.conectiva>
2001-03-15 12:24 ` Rik van Riel
2001-03-16 9:49 ` Stephen C. Tweedie
2001-03-16 11:50 ` Rik van Riel
2001-03-16 12:53 ` Stephen C. Tweedie
2001-03-18 7:23 ` Rik van Riel
2001-03-18 9:56 ` Mike Galbraith
2001-03-18 10:46 ` Rik van Riel
2001-03-18 12:33 ` Mike Galbraith
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.4.21.0103181122480.13050-100000@imladris.rielhome.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-kernel@conectiva.com.br \
--cc=mikeg@wen-online.de \
--cc=sct@conectiva.com.br \
/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