public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Jonathan George <Jonathan.George@trcinc.com>,
	"'matthew@mattshouse.com'" <matthew@mattshouse.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.0-test10 Sluggish After Load
Date: 05 Nov 2000 19:49:50 +0100	[thread overview]
Message-ID: <m3ofzufe41.fsf@linux.local> (raw)
In-Reply-To: <Pine.LNX.4.05.10011051433540.9109-100000@humbolt.nl.linux.org>

Hi Rik,

Rik van Riel <riel@conectiva.com.br> writes:
> On 4 Nov 2000, Christoph Rohland wrote:
> > I do see two problems here:
> > 1) shm_swap_core does not handle the failure of prepare_higmem_swapout
> >    right and basically cannot do so. It gets called zone independant
> >    and should probably get called per zone. At least it has to react:
> 
> AFAIC try_to_swap_out can handle this situation fine, it
> shouldn't be very difficult to get shm_swap to handle it
> too...

No I do not think that try_to_swap_out does handle this. It also
simply fails on this. I have seen lockups after try_to_swap_out
failing on prepare_higmem_swapout.

> > You see: you only have 5+27+27=59 pages under your control...
> 
> Ughhhh. Maybe we need some rebalancing there as well.
> That's a maximum of 5 pages of executable text mapped
> into all processes...

Yes, that's reasonable in my test case...

Greetings
                Christoph

-
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/

  reply	other threads:[~2000-11-05 18:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-01 15:44 2.4.0-test10 Sluggish After Load Jonathan George
2000-11-01 16:05 ` Rik van Riel
2000-11-03 12:54   ` Christoph Rohland
2000-11-04 13:05     ` Rik van Riel
2000-11-04 20:04       ` Christoph Rohland
2000-11-05 13:36         ` Rik van Riel
2000-11-05 18:49           ` Christoph Rohland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-01 16:18 Jonathan George
2000-11-01 16:56 ` Rik van Riel
2000-11-02  8:48   ` Christoph Rohland
2000-11-02 13:52     ` Rik van Riel
2000-11-02 16:22       ` matthew
2000-11-04  1:31         ` Peter Samuelson
2000-11-01 16:59 ` matthew
2000-11-01 17:11   ` Rik van Riel
2000-11-01 15:00 matthew
2000-11-01 15:26 ` Sean Hunter
2000-11-01 17:10   ` matthew
2000-11-01 17:13     ` Sean Hunter
2000-11-01 17:29       ` Rik van Riel
2000-11-02 11:09   ` Alessandro Suardi

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=m3ofzufe41.fsf@linux.local \
    --to=cr@sap.com \
    --cc=Jonathan.George@trcinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@mattshouse.com \
    --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