From: Chris Mason <mason@suse.com>
To: Andrew Morton <akpm@zip.com.au>, Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <andrea@suse.de>
Subject: Re: 2.4.14-pre6
Date: Thu, 01 Nov 2001 16:28:44 -0500 [thread overview]
Message-ID: <334750000.1004650124@tiny> (raw)
In-Reply-To: <3BE1B6CD.7DA43A6C@zip.com.au>
In-Reply-To: message from Linus Torvalds on Wednesday October 31, <Pine.LNX.4.33.0110310809200.32460-100000@penguin.transmeta.com> <15329.8658.642254.284398@notabene.cse.unsw.edu.au> <3BE1B6CD.7DA43A6C@zip.com.au>
On Thursday, November 01, 2001 12:55:41 PM -0800 Andrew Morton
<akpm@zip.com.au> wrote:
> Oh. I have a gripe concerning prune_icache(). The design
> idea behind keventd is that it's a "process context bottom
> half handler". It's used for things like cardbus hotplug
> interrupt handlers, handling tty hangups, etc. It should
> probably run SCHED_FIFO.
>
> Using keventd to synchronously flush large amounts of
> data out to disk constitutes gross abuse - it's being blocked
> from performing its designed duties for many seconds. Can we
> please not do that? We already have kswapd, kupdate, bdflush,
> which should be sufficient.
One of the worst parts of prune_icache was that if a journaled
FS needed to log dirty inodes, kswapd would wait on the log, who was
probably waiting on kswapd. Thus the dirty_inode call, which I'd like to
get rid of.
I don't think kupdate or bdflush are suitable to flush the dirty inodes,
kupdate shouldn't do memory pressure and bdflush shouldn't wait on the log.
So how about a new kinoded?
-chris
next prev parent reply other threads:[~2001-11-01 21:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 16:15 2.4.14-pre6 Linus Torvalds
2001-10-31 18:36 ` 2.4.14-pre6 Andrew Morton
2001-10-31 19:06 ` 2.4.14-pre6 Linus Torvalds
2001-11-01 10:20 ` 2.4.14-pre6 Neil Brown
2001-11-01 20:55 ` 2.4.14-pre6 Andrew Morton
2001-11-01 21:28 ` Chris Mason [this message]
2001-11-02 8:00 ` 2.4.14-pre6 Helge Hafting
2001-11-04 22:34 ` 2.4.14-pre6 Pavel Machek
2001-11-04 23:16 ` 2.4.14-pre6 Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2001-10-31 8:00 2.4.14-pre6 Linus Torvalds
2001-10-31 9:10 ` 2.4.14-pre6 Andrew Morton
2001-10-31 9:29 ` 2.4.14-pre6 Jens Axboe
2001-10-31 9:30 ` 2.4.14-pre6 bert hubert
2001-10-31 19:27 ` 2.4.14-pre6 Michael Peddemors
2001-10-31 19:38 ` 2.4.14-pre6 Linus Torvalds
2001-10-31 19:55 ` 2.4.14-pre6 Mike Castle
2001-10-31 20:02 ` 2.4.14-pre6 Rik van Riel
2001-10-31 23:18 ` 2.4.14-pre6 Erik Andersen
2001-10-31 23:40 ` 2.4.14-pre6 Dax Kelson
2001-10-31 23:57 ` 2.4.14-pre6 Michael Peddemors
2001-10-31 19:52 ` 2.4.14-pre6 Philipp Matthias Hahn
2001-10-31 21:05 ` 2.4.14-pre6 H. Peter Anvin
2001-11-01 19:14 ` 2.4.14-pre6 Pozsar Balazs
2001-11-02 12:01 ` 2.4.14-pre6 Pavel Machek
2001-11-05 20:43 ` 2.4.14-pre6 Charles Cazabon
2001-11-05 20:49 ` 2.4.14-pre6 Linus Torvalds
2001-11-05 21:27 ` 2.4.14-pre6 Josh Fryman
2001-11-05 19:04 ` 2.4.14-pre6 Gérard Roudier
2001-11-05 21:04 ` 2.4.14-pre6 Johannes Erdfelt
2001-11-05 21:08 ` 2.4.14-pre6 Wilson
2001-11-02 16:48 ` 2.4.14-pre6 jogi
2001-11-03 12:47 ` 2.4.14-pre6 Mike Galbraith
2001-11-03 18:01 ` 2.4.14-pre6 Linus Torvalds
2001-11-03 19:07 ` 2.4.14-pre6 Mike Galbraith
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=334750000.1004650124@tiny \
--to=mason@suse.com \
--cc=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.