mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: dcn@sgi.com (Dean Nelson)
Cc: linux-kernel@vger.kernel.org, nickpiggin@yahoo.com.au,
	Christoph Hellwig <hch@lst.de>
Subject: Re: kthread realtime priorities and exporting  sys_sched_setscheduler()
Date: Wed, 10 Nov 2004 11:14:52 -0800	[thread overview]
Message-ID: <20041110111452.1724b353.akpm@osdl.org> (raw)
In-Reply-To: <4192424B.mailxNJY11KR1G@aqua.americas.sgi.com>

dcn@sgi.com (Dean Nelson) wrote:
>
> I'm trying to push XP[C|NET] out to the community. (For further details:
> http://marc.theaimsgroup.com/?l=linux-ia64&m=109337050919186&w=2 )
> 
> An objection was raised over the exporting and calling of
> sys_sched_setscheduler(), which XPC calls to make its kthreads
> run at realtime priorities. Without this change we found that it
> was possible for user processes to be given a higher effective
> priority than the kthreads used by XPC. The upshot of this was
> that the latencies incurred by XPC increased 300 times in the
> test example given. If XPC's kthreads were given realtime
> priorities this did not happen. (For further details:
> http://marc.theaimsgroup.com/?l=linux-ia64&m=109337503100067&w=2 )

I'd disagree with Christoph on that.  Being able to set the scheduling
policy from a module-based kernel thread is a sensible thing to be able to
do, and you can do it by issuing a direct trap anyway.

EXPORT_SYMBOL_GPL() would be preferred.

Possibly it could be done by adding a variant of kthread_create() which has
a new `policy' argument, but it doesn't really seem worth the fuss.

      reply	other threads:[~2004-11-10 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 16:31 Dean Nelson
2004-11-10 19:14 ` Andrew Morton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041110111452.1724b353.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=dcn@sgi.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®