This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/18682] New: sched_get_priority_{min,max}(SCHED_OTHER) return 0 each
- From: "Ulrich.Windl at rz dot uni-regensburg.de" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 15 Jul 2015 14:27:51 +0000
- Subject: [Bug nptl/18682] New: sched_get_priority_{min,max}(SCHED_OTHER) return 0 each
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18682
Bug ID: 18682
Summary: sched_get_priority_{min,max}(SCHED_OTHER) return 0
each
Product: glibc
Version: 2.11
Status: NEW
Severity: normal
Priority: P2
Component: nptl
Assignee: unassigned at sourceware dot org
Reporter: Ulrich.Windl at rz dot uni-regensburg.de
CC: drepper.fsp at gmail dot com
Target Milestone: ---
In SLES11 SP3 on x86_64: When using sched_get_priority_{min,max}(SCHED_FIFO), I
get reasonable values (min=1, max=99). However when I use SCHED_OTHER, both
routines return 0.
My expectation was that for SCHED_OTHER the priorities would correspond to
nice() levels in some way, so that pthread_attr_setschedparam() would use that
value to try a renice of the thread.
(glibc-2.11.3-17.84.1)
--
You are receiving this mail because:
You are on the CC list for the bug.