From: Roger Larsson <roger.larsson@norran.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Anton Petrusevich <improvisus@echo.ru>,
linux-kernel@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Rik's VM contains a deadlock somewhere
Date: Tue, 19 Sep 2000 23:22:14 +0200 [thread overview]
Message-ID: <39C7D906.1AF31515@norran.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0009190720440.22122-100000@duckman.distro.conectiva>
Hi,
I too tested to stress the new VM
Quintelas mmap002 "deadlocks" for me.
PPro, 96 MB, UP
active: 22337 (I think this varies, have too lock a 2nd time)
inactive_dirty: 324 varies
inactive_clean: 0
free: 288
... 1x 512 = 512 kB
... 2 x 16 + 1 x 32 + 1 x 64 = 640 kB
My feeling when looking at Alt-SysRq-M was
that pages was moved between Active and
idle_dirty - will look into this.
There is no 'if (current->need_resched) schedule()'
in this code - if kswapd starts too loop...
PS
Now I am back from my vacation period...
DS
Rik van Riel wrote:
>
> On Tue, 19 Sep 2000, Anton Petrusevich wrote:
>
> > please, check carefully Rik's VM patch, it definitly contains a
> > deadlock, which can be seen on low-memory computers. Try mem=8m. I
> > wasn't able to use any Rik patch since against -test8 (-t8-vmpatch{2,4},
> > -test9-pre{1,2}). It boots fine(mem=16m), but then stalls begin for some
> > time and for infinitive time at last. I told Rik about it, he tried to
> > fix but wasn't successful.
> >
> > With mem=8m it couldn't finish init scripts even.
>
> I /thought/ I had fixed this, since the system runs fine
> on my (SMP, SCSI) test machine when I boot it with mem=8m.
>
> Somebody on IRC suggested to me that this may be an UP-only
> bug ... I'm looking into this and hope to fix it soon, but
> I have to admit some help would be welcome ;)
>
> (I'm still at Linux Kongress and won't be back in the office
> for about a week)
>
> regards,
>
> Rik
> --
> "What you're running that piece of shit Gnome?!?!"
> -- Miguel de Icaza, UKUUG 2000
>
> http://www.conectiva.com/ http://www.surriel.com/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
--
Home page:
http://www.norran.net/nra02596/
--
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/
parent reply other threads:[~2000-09-19 21:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.21.0009190720440.22122-100000@duckman.distro.conectiva>]
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=39C7D906.1AF31515@norran.net \
--to=roger.larsson@norran.net \
--cc=improvisus@echo.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@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