From: Rik van Riel <riel@conectiva.com.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-mm@kvack.org, Marcelo Tosatti <marcelo@conectiva.com.br>,
Jari Ruusu <jari.ruusu@pp.inet.fi>
Subject: Re: VM problem with 2.4.8-ac9 (fwd)
Date: Wed, 22 Aug 2001 18:34:34 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0108221833470.31410-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <E15ZfdG-0002M4-00@the-village.bc.nu>
On Wed, 22 Aug 2001, Alan Cox wrote:
> > The strange thing is that the recent vm tweaks don't
> > have any influence on the code paths which could cause
> > tasks segfaulting ...
>
> They change reuse and timing patterns. I can believe we may have
> bugs left over from before that are now showing up.
The swap code is my usual suspect in this case, since
I'm still not sure how the locking in that part of the
VM is supposed to work. :|
cheers,
Rik
--
IA64: a worthy successor to the i860.
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com/
--
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-mm.org/
next prev parent reply other threads:[~2001-08-22 21:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 19:25 Rik van Riel
2001-08-22 18:27 ` Marcelo Tosatti
2001-08-23 8:25 ` Jari Ruusu
2001-08-23 17:35 ` Jari Ruusu
2001-08-23 20:24 ` Hugh Dickins
2001-08-23 20:29 ` Alan Cox
2001-08-23 20:37 ` Rik van Riel
2001-08-24 17:23 ` Jari Ruusu
2001-08-24 17:41 ` Alan Cox
2001-08-24 18:40 ` Marcelo Tosatti
2001-08-24 20:11 ` Rik van Riel
2001-08-25 13:10 ` Jari Ruusu
2001-08-28 15:49 ` Jari Ruusu
2001-08-22 21:14 ` Alan Cox
2001-08-22 21:28 ` Rik van Riel
2001-08-22 21:33 ` Alan Cox
2001-08-22 20:03 ` Marcelo Tosatti
2001-08-22 21:34 ` Rik van Riel [this message]
2001-08-23 6:19 ` Eric W. Biederman
2001-08-23 12:53 ` Alan Cox
2001-08-23 13:18 ` Rik van Riel
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.33L.0108221833470.31410-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jari.ruusu@pp.inet.fi \
--cc=linux-mm@kvack.org \
--cc=marcelo@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