#11755 closed enhancement (duplicate)
[PATCH] Implement getpriority and setpriority
| Reported by: | Timothy_Gu | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/POSIX | Version: | R1/Development |
| Keywords: | gci2014 | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Attachments (2)
Change History (8)
comment:1 by , 10 years ago
| patch: | 0 → 1 |
|---|
by , 10 years ago
| Attachment: | 0001-libroot-add-gs-etpriority-implementation.2.patch added |
|---|
by , 10 years ago
| Attachment: | 0001-libroot-add-gs-etpriority-implementation.patch added |
|---|
comment:2 by , 10 years ago
Another question is if we should make the priority notation conversion functions public.
follow-up: 5 comment:3 by , 10 years ago
| Blocked By: | 2817 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
You should attach your patches to the existing ticket #2817 directly instead of opening a new one.
comment:4 by , 10 years ago
| Blocked By: | 2817 removed |
|---|
(In #2817) There is a limitation with the approach you implemented in these patches: the priority only applies to existing threads. As discussed in this ticket, a better solution would be to have a process-global "nice" value and also use it when creating new threads to adjust their priorities.
comment:5 by , 10 years ago
Replying to pulkomandy:
You should attach your patches to the existing ticket #2817 directly instead of opening a new one.
On the GCI task it is said to:
Open a new trac ticket and attach your patch to it.
Note:
See TracTickets
for help on using tickets.
Patch