From: "Thomas Langås" <tlan@stud.ntnu.no>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "Thomas Langås" <tlan@stud.ntnu.no>,
"Ragnar Kjørstad" <kernel@ragnark.vestdata.no>,
linux-mm@kvack.org
Subject: Re: SMP/highmem problem
Date: Tue, 22 May 2001 02:07:43 +0200 [thread overview]
Message-ID: <20010522020742.A20434@flodhest.stud.ntnu.no> (raw)
In-Reply-To: <Pine.LNX.4.21.0105182307230.5531-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Fri, May 18, 2001 at 11:10:36PM -0300
Rik van Riel:
> > 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
I added a counter which didn't "goto try_again" if it hit 10.
> 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
Made this function do return MIN(sum, ZONE_DMA+ZONE_NORMAL)
This did actually improve things _alot_ :) We're going to perform some more
tests sometime tomorrow, but as far as I can tell, things are going way
better now than they did before. However, it might not be perfect yet...
--
-Thomas
--
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/
prev parent reply other threads:[~2001-05-22 0:07 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
2001-05-22 0:07 ` Thomas Langås [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=20010522020742.A20434@flodhest.stud.ntnu.no \
--to=tlan@stud.ntnu.no \
--cc=kernel@ragnark.vestdata.no \
--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