From: Rik van Riel <riel@nl.linux.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux MM <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.rutgers.edu>,
Andrea Arcangeli <andrea@e-mind.com>
Subject: [patch] 2.2.15-pre3 kswapd fix
Date: Fri, 21 Jan 2000 02:55:19 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.10001210252390.27593-100000@mirkwood.dummy.home> (raw)
Hi Alan,
here's a much cleaner (and hopefully slightly higher
performance) fix of the kswapd problem. The code is
also more readable now...
About Andrea's freepages.low vs. freepages.min problem,
I propose we chose .low here since it's value is higher
and we're trying to solve a reliability problem here.
We'll find out what to do with the freepages.min once
we need it ... in 2.3 it _will_ be used.
regards,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
--- linux-2.2.15-pre3/mm/vmscan.c.orig Wed Jan 19 21:18:54 2000
+++ linux-2.2.15-pre3/mm/vmscan.c Fri Jan 21 02:46:42 2000
@@ -485,18 +485,16 @@
* the processes needing more memory will wake us
* up on a more timely basis.
*/
- interruptible_sleep_on_timeout(&kswapd_wait, HZ);
while (nr_free_pages < freepages.high)
{
- if (do_try_to_free_pages(GFP_KSWAPD))
- {
- if (tsk->need_resched)
- schedule();
- continue;
- }
- tsk->state = TASK_INTERRUPTIBLE;
- schedule_timeout(10*HZ);
+ if (!do_try_to_free_pages(GFP_KSWAPD))
+ break;
+ if (tsk->need_resched)
+ schedule();
}
+ run_task_queue(&tq_disk);
+ tsk->state = TASK_INTERRUPTIBLE;
+ schedule_timeout(HZ);
}
}
@@ -509,18 +507,16 @@
* from user processes, because the locking issues are
* nasty to the extreme (file write locks, and MM locking)
*
- * One option might be to let kswapd do all the page-out
- * and VM page table scanning that needs locking, and this
- * process thread could do just the mmap shrink stage that
- * can be done by just dropping cached pages without having
- * any deadlock issues.
+ * If we're on or just slighly below freepages.low, kswapd
+ * should manage on its own, we just give it a nudge. This
+ * should also reduce contention for the kernel lock above.
*/
int try_to_free_pages(unsigned int gfp_mask)
{
int retval = 1;
wake_up_interruptible(&kswapd_wait);
- if (gfp_mask & __GFP_WAIT)
+ if ((gfp_mask & __GFP_WAIT) && (nr_free_pages < (freepages.low - 4)))
retval = do_try_to_free_pages(gfp_mask);
return retval;
}
--- linux-2.2.15-pre3/mm/page_alloc.c.orig Wed Jan 19 21:32:05 2000
+++ linux-2.2.15-pre3/mm/page_alloc.c Wed Jan 19 21:42:00 2000
@@ -212,7 +212,7 @@
if (!(current->flags & PF_MEMALLOC)) {
int freed;
- if (nr_free_pages > freepages.min) {
+ if (nr_free_pages > freepages.low) {
if (!low_on_memory)
goto ok_to_allocate;
if (nr_free_pages >= freepages.high) {
--
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.nl.linux.org/Linux-MM/
next reply other threads:[~2000-01-21 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 1:55 Rik van Riel [this message]
2000-01-21 2:18 ` Andrea Arcangeli
2000-01-21 2:29 ` Rik van Riel
2000-01-21 13:02 ` Andrea Arcangeli
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.10.10001210252390.27593-100000@mirkwood.dummy.home \
--to=riel@nl.linux.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@e-mind.com \
--cc=linux-kernel@vger.rutgers.edu \
--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