[lkml]   [2015]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH RFC] nohz,blk-mq: do not create blk-mq workqueues on nohz dedicated CPUs
On Tue, 2015-03-31 at 10:27 -0400, Rik van Riel wrote:
> CPUs with nohz_full do not want disruption from timer interrupts,
> or other random system things. This includes block mq work.
> There is another issue with block mq vs. realtime tasks that run
> 100% of the time, which is not uncommon on systems that have CPUs
> dedicated to real time use with isolcpus= and nohz_full=
> Specifically, on systems like that, a block work item may never
> get to run, which could lead to filesystems getting stuck forever.

What reason is there to run a compute hog as RT if it's the only task
on an isolated core? In an RT kernel, PI may be a reason, but if a
task is so critical that it needs bare metal, it had better not be.


 \ /
  Last update: 2015-04-05 08:01    [W:0.098 / U:1.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site