From: Rik van Riel <riel@conectiva.com.br>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-mm@kvack.org
Subject: Re: VM problem with 2.4.8-ac9 (fwd)
Date: Thu, 23 Aug 2001 10:18:47 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0108231017320.5646-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <m1zo8rl2lt.fsf@frodo.biederman.org>
On 23 Aug 2001, Eric W. Biederman wrote:
> Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> > > Suspect code would be:
> > > - tlb optimisations in recent -ac (tasks dying with segfault)
>
> Can I ask which tlb optimisations these are.
> It is so weird I have been having a hard time believing the bug
> reports.
We found a new suspect last night. Turns out Linus'
locking overhaul of memory.c results not only in the
kernel dropping locks in critical sections, but also
possibly ends up in the pageout path ...
regards,
Rik
--
IA64: a worthy successor to i860.
http://www.surriel.com/ http://distro.conectiva.com/
Send all your spam to aardvark@nl.linux.org (spam digging piggy)
--
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/
prev parent reply other threads:[~2001-08-23 13:18 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
2001-08-23 6:19 ` Eric W. Biederman
2001-08-23 12:53 ` Alan Cox
2001-08-23 13:18 ` Rik van Riel [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=Pine.LNX.4.33L.0108231017320.5646-100000@imladris.rielhome.conectiva \
--to=riel@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--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