From: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
To: H.H.vanRiel@fys.ruu.nl
Cc: Perry Harrington <pedward@sun4.apsoft.com>,
linux-kernel@vger.rutgers.edu, linux-mm <linux-mm@kvack.org>
Subject: Re: new kmod.c - debuggers and testers needed
Date: Mon, 20 Apr 1998 23:00:14 +0100 [thread overview]
Message-ID: <199804202200.XAA03999@dax.dcs.ed.ac.uk> (raw)
In-Reply-To: <Pine.LNX.3.91.980414200024.1070J-100000@mirkwood.dummy.home>
Hi,
On Tue, 14 Apr 1998 20:02:09 +0200 (MET DST), Rik van Riel
<H.H.vanRiel@fys.ruu.nl> said:
> 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.
bdflush does nothing except IO, so there's no real reason to
twin-thread it. kswapd does indeed benefit from a separate IO thread,
and I've already got patches which implement a kswiod for IO and a
kswapd for page scanning. I'll post them once I've got them ready
against the latest kernel: my current patches for this code are pretty
old.
--Stephen
prev parent reply other threads:[~1998-04-20 22:14 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 ` Rik van Riel
1998-04-14 21:27 ` Perry Harrington
1998-04-14 22:58 ` Kswapd future (was: Re: new kmod.c - debuggers and testers needed) Rik van Riel
1998-04-14 23:13 ` new kmod.c - debuggers and testers needed Benjamin C.R. LaHaise
1998-04-20 22:00 ` Stephen C. Tweedie [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=199804202200.XAA03999@dax.dcs.ed.ac.uk \
--to=sct@dcs.ed.ac.uk \
--cc=H.H.vanRiel@fys.ruu.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