From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: "Dr. Werner Fink" <werner@suse.de>
Cc: linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: [2x PATCH] page map aging & improved kswap logic
Date: Fri, 27 Feb 1998 10:58:34 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980227105614.17899A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199802270929.KAA28081@boole.fs100.suse.de>
On Fri, 27 Feb 1998, Dr. Werner Fink wrote:
> > The kswapd logic is almost completely redone. Basically,
> > kswapd tries (free_pages_high - nr_free_pages) times to
> > free a page, but when memory becomes tighter, the number
> > of tries become even higher.
>
> Is the explicit call of run_task_queue(&tq_disk) really needed?
> Maybe setting of the __GFP_WAIT flag would work in the same manner:
>
> gfp_mask = __GFP_IO;
> if (atomic_read(&nr_async_pages) >= SWAP_CLUSTER_MAX)
> gfp_mask |= __GFP_WAIT;
Wouldn't that just mean that the pages that are
swapped out from now on will be done synchronously?
What I wanted kswapd to do, was to select SWAP_CLUSTER_MAX
pages and swap them out in _one_ I/O operation. Because
this should save head movement, it might give us an improvement
over syncing each swapped page seperately.
Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+
next parent reply other threads:[~1998-02-27 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199802270929.KAA28081@boole.fs100.suse.de>
1998-02-27 9:58 ` Rik van Riel [this message]
1998-02-27 19:52 ` Stephen C. Tweedie
1998-02-27 22:28 ` Benjamin C.R. LaHaise
1998-02-26 21:00 Rik van Riel
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.3.91.980227105614.17899A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=werner@suse.de \
/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