> keventd is a "process context bottom half handler". It's designed
> for use by interrupt handlers for handing off awkward, occasional
> things which need process context. For example, device hotplugging,
> which was the original reason for its introduction.
> So it makes sense to give keventd SCHED_RR policy and maximum
> priority. Which should fix this problem as well, yes?
Next to ditching keventd, this is probably the best thing we can do.
I wonder how much code _really_ needs it - that is, what really needs to
be running in process-context? Obviously device hotplug probably does.
But for things like that, what about spawning (temporarily) a kernel
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/