On Thu, 22 Oct 2015, Tejun Heo wrote: > > Hmmm? Just use a dedicated workqueue with WQ_MEM_RECLAIM. If > > concurrency management is a problem and there's something live-locking > > for that work item (really?), WQ_CPU_INTENSIVE escapes it. If this is > > a common occurrence that it makes sense to give vmstat higher > > priority, set WQ_HIGHPRI. > > Oooh, HIGHPRI + CPU_INTENSIVE immediate scheduling guarantee got lost > while converting HIGHPRI to a separate pool but guaranteeing immediate > scheduling for CPU_INTENSIVE is trivial. If vmstat requires that, > please let me know.
I guess we need that otherwise vm statistics are not updated while worker threads are blocking on memory reclaim. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
