From: Jim Cromie <jim.cromie@domain.hid>
To: Romain Lenglet <rlenglet@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] xeno-test manpage patch
Date: Fri, 28 Apr 2006 11:10:53 -0400 [thread overview]
Message-ID: <4452307D.5060108@domain.hid> (raw)
In-Reply-To: <200604251502.12312.rlenglet@domain.hid>
Romain Lenglet wrote:
> Added documentation for the new -U option, and did some cleanups.
>
FYI,
a few *tiny* issues.
-d eg: /dev/hda1 might be better than /dev/hda/, and drop trailing slash.
-m, -M. log-file not required.
-N path can be /absolute too, not just ../relative
-p 'cmd' no longer run between latencies, just before & after
pass-thru:
-s -T 10 -q the 10 is now 120.
more subtly - your intro doesnt express the defaulting behavior that
this section does describe.
any pass-thru provided with turn off those defaults, so if you just use
-h, the test will output lines
each second, and never finish, so you dont get histogram (IIRC - you may
get it from ^C handler).
Im not at all sure its worth touching, and I should probably change the
defaults to add histogram,
and drop quiet.
-h implies -s (its just easier that way)
-- needed by testsuite/*/run scripts, not by xeno-test. I dont recall
every using it.
BUGS
-N name is timestamped, giving uniqueness. This is a caveat, not a bug
-p oops. Im open to suggestions whether this is worth fixing.
(workload mgmt)
workload tasks arent always (ever?) restarted once they finish,
so a real /dev/hda1 workload may end before your test does, causing
non-uniform &
unexpected load variations.
workloads arent always killed if test is interrupted.
thanks,
jimc
next prev parent reply other threads:[~2006-04-28 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 6:02 [Xenomai-core] xeno-test manpage patch Romain Lenglet
2006-04-25 11:31 ` Jim Cromie
2006-04-28 15:10 ` Jim Cromie [this message]
2006-04-29 9:03 ` Romain Lenglet
2006-04-30 14:17 ` Philippe Gerum
2006-05-01 18:44 ` Jim Cromie
2006-05-02 2:58 ` Romain Lenglet
2006-05-02 22:25 ` Thomas Lockhart
2006-05-03 6:09 ` Romain Lenglet
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=4452307D.5060108@domain.hid \
--to=jim.cromie@domain.hid \
--cc=rlenglet@domain.hid \
--cc=xenomai@xenomai.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.