#99 Error setting RT scheduling priority

closed
nobody
5
2005-05-05
2004-11-24
Anonymous
No

dao/dao.c calls setRealTimeScheduling to set the reader
to priority=4 and the writer to 5.

dao/port.cc, POSIX scheduling section, *subtracts* this
from sched_get_priority_max(SCHED_RR). But RT
priorities are, unlike nice, bigger number = higher
priority.

I believe this is why cdrdao turns my asterisk into a
gibbering idiot.

No patch - the fix should be obvious and trivial :-).
Even better would be an option so the RT priority could
be changed. Mind you, I could make the same request of
asterisk...

Discussion

  • Logged In: NO

    Ah... forgot to login :-(

    Mike Jagdis <mjagdis@eris-associates.co.uk>

     
  • Denis Leroy
    Denis Leroy
    2005-05-03

    Logged In: YES
    user_id=95186

    But the priority is substracted from the MAXIMUM priority
    setting, so this is doing what it's supposed to do. FYI,
    minimum setting is usually 1, while maximum is 99. You can't
    use a setting above 99, obviously. It's therefore using 95
    for the reader thread and 94 for the writer thread. I don't
    see where the problem is... Sure,you can try with different
    values (99 for reader, 98 for writer ??). Let me know if
    different values work better for you...

     
  • Denis Leroy
    Denis Leroy
    2005-05-05

    • status: open --> closed