Re: setting task->ioprio from a kernel thread
From: Jens Axboe
Date: Fri Jul 29 2005 - 02:36:12 EST
On Mon, Jul 25 2005, Zach Brown wrote:
> 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?
I guess the sys_get/set export would be ok, although it seems a little
nasty to export the actual syscalls.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/