> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/