From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Perry Harrington <pedward@sun4.apsoft.com>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Kswapd future (was: Re: new kmod.c - debuggers and testers needed)
Date: Wed, 15 Apr 1998 00:58:58 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.91.980415005704.875A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199804142127.OAA09136@sun4.apsoft.com>
On Tue, 14 Apr 1998, Perry Harrington wrote:
> > On Tue, 7 Apr 1998, Perry Harrington wrote:
> >
> > > Threads
> > > are useful in their appropriate context, and kswapd, and kmod would benefit
> > > from them.
> >
> > Hmm, maybe it would be useful for kswapd and bdflush to fork()
> > off threads to do the actual disk I/O, so the main thread won't
> > be blocked and paused... This could remove some bottlenecks.
>
> I was thinking that kswapd could use some of it's spare time to do an LRU
> paging scan, consolidate free space, and possibly do remapping of process
> memory spaces to make them more efficient (map pages to contiguous chunks
> of memory and swap).
Unfortunately, kswapd doesn't have such a thing as 'spare time'.
It is a kernel daemon that does what's neccessary, but we want
to keep it's CPU/IO footprint absolutely minimal since all other
applications are more important...
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.fys.ruu.nl/~riel/ | <H.H.vanRiel@fys.ruu.nl> |
+-------------------------------------------+--------------------------+
next prev parent reply other threads:[~1998-04-15 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199804080001.RAA23780@sun4.apsoft.com>
1998-04-14 18:02 ` new kmod.c - debuggers and testers needed Rik van Riel
1998-04-14 21:27 ` Perry Harrington
1998-04-14 22:58 ` Rik van Riel [this message]
1998-04-14 23:13 ` Benjamin C.R. LaHaise
1998-04-20 22:00 ` Stephen C. Tweedie
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.980415005704.875A-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=pedward@sun4.apsoft.com \
/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