All of lore.kernel.org
 help / color / mirror / Atom feed
* Workqueue scheduling policy
@ 2013-08-15 20:59 spdev31
  2013-08-19 16:24 ` Steven Rostedt
  0 siblings, 1 reply; 2+ messages in thread
From: spdev31 @ 2013-08-15 20:59 UTC (permalink / raw)
  To: linux-rt-users

Hi,

I see the workqueue scheduling policys defaults to SCHED_FIFO with the
2.6.33 RT patch but is SCHED_NORMAL with the 3.0 RT patch (and newer
RT patches, I believe).  Can you help me understand the reason for
using realtime policies for 2.6.33 RT workqueues and non-realtime
policies for 3.0 RT patch workqueues?

Thanks,
Shaun

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Workqueue scheduling policy
  2013-08-15 20:59 Workqueue scheduling policy spdev31
@ 2013-08-19 16:24 ` Steven Rostedt
  0 siblings, 0 replies; 2+ messages in thread
From: Steven Rostedt @ 2013-08-19 16:24 UTC (permalink / raw)
  To: spdev31; +Cc: linux-rt-users

On Thu, 15 Aug 2013 13:59:49 -0700
spdev31 <spdev31@gmail.com> wrote:

> Hi,
> 
> I see the workqueue scheduling policys defaults to SCHED_FIFO with the
> 2.6.33 RT patch but is SCHED_NORMAL with the 3.0 RT patch (and newer
> RT patches, I believe).  Can you help me understand the reason for
> using realtime policies for 2.6.33 RT workqueues and non-realtime
> policies for 3.0 RT patch workqueues?
> 

Actually, mainline kernel set workqueues as SCHED_FIFO for 2.6.33 and
no longer does that for 3.0 kernels. Has nothing to do with the -rt
patch.

But as for why they did that switch. Probably because there's no reason
that the workqueues need to be running as a high priority task, just
like ksoftirqd runs as SCHED_OTHER in mainline.

-- Steve

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-08-19 16:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-15 20:59 Workqueue scheduling policy spdev31
2013-08-19 16:24 ` Steven Rostedt

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.