Skip to contentSkip to conversation

How do I raise a thread to realtime priority?

DISCUSSION Robin Holt 3 participants 4 messages Feb 12, 2004

lore
Share & tools
lore

Robin Holt

author
#0 lore raw

In the 2.4 kernel headers, unistd.h had a _syscall3 that I could use to make an extern of the sys_sched_setscheduler raise a tasks priority to realtime. With 2.6, the _syscall3 has been replaced with static inlines. This all seems well.

Since sys_sched_setscheduler is not in the unistd.h, should I add it to unistd.h? Is there a prefered method for exporting/inlining syscall entry points?

Thanks,
Robin Holt

#1 lore raw
Quoted 8 lines · Robin Holt

In the 2.4 kernel headers, unistd.h had a _syscall3 that I could use to make an extern of the sys_sched_setscheduler raise a tasks priority to realtime. With 2.6, the _syscall3 has been replaced with static inlines. This all seems well.

Since sys_sched_setscheduler is not in the unistd.h, should I add it to unistd.h? Is there a prefered method for exporting/inlining syscall entry points?

libc "exports syscall entry points" -- call sched_setscheduler(). That works on 2.4 and 2.6.

Signature · 6 lines
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain
author
#2 lore raw
In reply to Robin Holt
Quoted 6 lines · Matthew Wilcox
Quoted 5 lines · Robin Holt

In the 2.4 kernel headers, unistd.h had a _syscall3 that I could use to make an extern of the sys_sched_setscheduler raise a tasks priority to realtime. With 2.6, the _syscall3 has been replaced with static inlines. This all seems well.

Quoted 6 lines
Quoted 3 lines

Since sys_sched_setscheduler is not in the unistd.h, should I add it to unistd.h? Is there a prefered method for exporting/inlining syscall entry points?

libc "exports syscall entry points" -- call sched_setscheduler(). That works on 2.4 and 2.6.

Maybe I wasn't clear. This is a kernel thread that is trying to raise priority.

#3 lore raw
In reply to Robin Holt

On Thu, 12 Feb 2004 16:17:52 -0600 Robin Holt <[email protected]> wrote:

| On Thu, Feb 12, 2004 at 10:08:20PM +0000, Matthew Wilcox wrote:
| > On Thu, Feb 12, 2004 at 03:53:57PM -0600, Robin Holt wrote:
| > > In the 2.4 kernel headers, unistd.h had a _syscall3 that I could
| > > use to make an extern of the sys_sched_setscheduler raise a tasks
| > > priority to realtime.  With 2.6, the _syscall3 has been replaced
| > > with static inlines.  This all seems well.
| > > 
| > > Since sys_sched_setscheduler is not in the unistd.h, should I add
| > > it to unistd.h?  Is there a prefered method for exporting/inlining
| > > syscall entry points?
| > 
| > libc "exports syscall entry points" -- call sched_setscheduler().
| > That works on 2.4 and 2.6.
| 
| Maybe I wasn't clear.  This is a kernel thread that is trying to
| raise priority.

I have patches in progress (in -mm) that add this and other syscalls to include/linux/syscalls.h (for non-arch-specific) and to include/asm-*/unistd.h for arch-specific syscalls.

--
~Randy