From: Jan Kiszka <jan.kiszka@domain.hid>
To: niklaus.giger@domain.hid
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [RFC] collecting xenomai statistics
Date: Mon, 17 Apr 2006 23:13:00 +0200 [thread overview]
Message-ID: <444404DC.60905@domain.hid> (raw)
In-Reply-To: <200604171047.51730.niklaus.giger@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]
Niklaus Giger wrote:
> Hi
>
> Following a suggestion from Philippe Gerum I propose to collect and prepare
> like this:
>
> a) Make it easy to collect information
>
> add -s/-c option to xeno-test, help text would look like
> -s send output of xeno-test to xeno-stat@domain.hid
> -c <name> if -s, send also kernel config file to xeno-stat@domain.hid
> (May be patch xeno-config to emit also the revision of the svn checkout?)
>
> b) Setup an e-mail account xeno-stat@domain.hid.
>
> c) Add a archiver which generates daily a gzipped tar file of all messages
> ever sent to xeno-stat@domain.hid (e.g. of its mbox). Make it available
> somewhere on the internet.
>
> d) Write a converter the raw messages into more suitable representation, eg. a
> MySQL-DB, a spreadsheet format. Extract the raw message and kernel config and
> store the publicly accessible on the internet. The DB/spreadsheet will
> contain pointers (URLs) to the raw message/kernel config.
>
> e) Write viewers which present interesting statistics. E.g. X/HTML pages to
> present a ordered (by architecture, board, version, etc) view of the
> available results.
Do you know http://issaris.org/rtai (the RTAI LiveCD)? It's no longer
maintained but may still contain useful ideas, and Takis (Panagiotis
Issaris) will likely be happy to answer questions on details of his
approach.
>
> I would like to advance like this:
>
> I am not interested in step a), as it is easy for me just to write a trivial
> script to sent the xeno-test output to any address. Also adding the revision
> of svn checkout is not very difficult.
>
> For point b+c) I am lacking the necessary rights, but it easy for me to setup
> a similar account for my tests here. But I would appreciate, if somebody of
> the core team would help me to get this work done.
>
> For point d+e) I will (after a week of vacation with my son) invest some work.
> But I would be very interested in knowing exactly which kind of information
> the core developers are interested in. How should it be presented? In tabular
> form? Graphs, which ones? And kind of feedback will be evaluated and
> integrated.
>
I think starting with what Takis once collected would be more than
enough for a first round.
I cannot provide you access to the infrastructure, but I vote for
granting it. Great commitment!
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-04-17 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 8:47 [Xenomai-core] [RFC] collecting xenomai statistics Niklaus Giger
2006-04-17 21:13 ` Jan Kiszka [this message]
2006-04-18 2:10 ` Jim Cromie
2006-04-18 15:32 ` [Xenomai-core] [patch] xeno-test email addition Jim Cromie
2006-04-18 15:58 ` Philippe Gerum
2006-04-19 3:55 ` Romain Lenglet
2006-04-19 9:01 ` Philippe Gerum
2006-04-19 12:52 ` Jim Cromie
2006-04-20 21:01 ` Philippe Gerum
2006-04-18 17:02 ` [Xenomai-core] [RFC] collecting xenomai statistics Gilles Chanteperdrix
2006-04-18 17:15 ` Gilles Chanteperdrix
2006-04-18 17:39 ` Gilles Chanteperdrix
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=444404DC.60905@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=niklaus.giger@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.