From: Rik van Riel <riel@conectiva.com.br>
To: "Thomas Langås" <tlan@stud.ntnu.no>
Cc: "Ragnar Kjørstad" <kernel@ragnark.vestdata.no>, linux-mm@kvack.org
Subject: Re: SMP/highmem problem
Date: Fri, 18 May 2001 23:10:36 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0105182307230.5531-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <20010519013544.A21549@flodhest.stud.ntnu.no>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1527 bytes --]
On Sat, 19 May 2001, [iso-8859-1] Thomas Langas wrote:
> Rik van Riel:
> > A few fixes for this situation have gone into 2.4.5-pre2 and
> > 2.4.5-pre3. If you have the time, could you test if this problem
> > has gotten less or has gone away in the latest kernels ?
>
> Ok, now we've tested 2.4.5-pre3, and it's still like described before.
> However, it's a bit better.
Whooops, now that I looked at the source code for -pre3
I realise the particular patch which could fix this
problem hasn't gone into -pre3.
I'll send a patch SOON (almost like the one I sent a
few days ago, but with a few new fixes which have been
accumulating in the last few days).
> So, any other ideas are very welcome :)
The basis for the patch will be the page_alloc.c VM
patch on http://www.surriel.com/patches/, but with 2
minor changes:
1) don't allow GFP_BUFFER pages to loop in __alloc_pages(),
but have them fail after a while ... needed to avoid
deadlocks
2) never allow nr_free_buffer_pages to return a number
larger than how many dirty pages would reasonably fit
in ZONE_DMA and ZONE_NORMAL ... should fix your problem
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://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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-19 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 18:39 Ragnar Kjørstad
2001-05-17 19:19 ` Rik van Riel
2001-05-18 23:35 ` Thomas Langås
2001-05-19 2:10 ` Rik van Riel [this message]
2001-05-22 0:07 ` Thomas Langås
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.0105182307230.5531-100000@imladris.rielhome.conectiva \
--to=riel@conectiva.com.br \
--cc=kernel@ragnark.vestdata.no \
--cc=linux-mm@kvack.org \
--cc=tlan@stud.ntnu.no \
/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