From: Jens Axboe <axboe@suse.de>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setting task->ioprio from a kernel thread
Date: Fri, 29 Jul 2005 09:36:44 +0200 [thread overview]
Message-ID: <20050729073643.GE22569@suse.de> (raw)
In-Reply-To: <42E5BC9C.8060803@oracle.com>
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.
--
Jens Axboe
prev parent reply other threads:[~2005-07-29 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 4:31 setting task->ioprio from a kernel thread Zach Brown
2005-07-29 7:36 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050729073643.GE22569@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox