Messages in this thread | | | Date | Mon, 25 Jul 2005 21:31:24 -0700 | From | Zach Brown <> | Subject | setting task->ioprio from a kernel thread |
| |
In OCFS2 there is currently an in-kernel heartbeat thread that really wants to communicate liveness to other nodes as quickly as possible by writing to a block device. Setting aside the specific wisdom of a kernel heartbeat thread for a bit, has it been considered that kernel threads might want to set their io priority with the task->ioprio bits? Neither set_task_ioprio() nor sys_ioprio_set() seem to be accessible to modules and open-coding it is clearly a bad idea. Would the universe be opposed to a _GPL() export of, say, the sys_() interface?
- z - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |