From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [git pull] schedutils
Date: Thu, 21 Jul 2011 17:43:03 +0200 [thread overview]
Message-ID: <20110721154303.GF22568@nb.net.home> (raw)
In-Reply-To: <CAG27Bk3vs54m7b6y_M_uq4RuyPBn-yhAEt2GhicsyY8F_+jJfw@mail.gmail.com>
On Wed, Jul 20, 2011 at 10:15:13AM +0200, Sami Kerola wrote:
> >> - ioprio = strtol_or_err(optarg, _("failed to parse class data"));
> >> + ioprio = strtol_or_err(optarg, _("failed to parse priority"));
> >
> > well, the original kernel Documentation/block/ioprio.txt is talking
> > about "class data" and I think it would be better to follow kernel
> > here. Maybe one day the mask for the syscall will used for a different
> > things than only for priority...
>
> I read kernel documentation using priority, class data and level as
> synonyms. To me the `class data' is most confusing because it gets
> mixed up with `class'. As you did not like `priority' I do my last
> attempt to change the word and used `level'. How that would sound?
The 'ioprio' in the syscall:
syscall(SYS_ioprio_set, which, who, ioprio);
encodes two information:
IOPRIO_PRIO_CLASS - e.g. realtime, idle, ...
IOPRIO_PRIO_DATA - e.g. 0-7
this is reason why the docs is talking about "class" and "class data".
Anyway, merged with some minor changes and --classdata option :-)
Minor notes:
* .PP in man page within .IP block does not have the same meaning
like blank line
* I think that
-c, --class NUM
is better than
-c, --class=NUM
I have fixed this in ionice man page, but not in usage(). It would be
nice to use in all man pages and usage() functions the same syntax.
Maybe we can create any template or so to have it documented.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-07-21 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 18:37 [git pull] schedutils Sami Kerola
2011-07-18 22:17 ` Karel Zak
2011-07-20 8:15 ` Sami Kerola
2011-07-21 15:43 ` Karel Zak [this message]
2011-07-21 18:37 ` Sami Kerola
2011-07-21 19:03 ` Karel Zak
2011-07-21 20:03 ` Sami Kerola
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=20110721154303.GF22568@nb.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@gmail.com \
--cc=util-linux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.