From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Mathew Benson <mathew.benson@gmail.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Resource utilization
Date: Wed, 7 Jan 2015 15:06:51 +0100 [thread overview]
Message-ID: <20150107140651.GA10298@hermes.click-hack.org> (raw)
In-Reply-To: <3FCA47A3-7859-424A-B427-B2C45939C567@gmail.com>
On Wed, Jan 07, 2015 at 05:06:43AM -0800, Mathew Benson wrote:
> Heap utilization,
> cache faults, page faults, BSS size, thread
> stack high water mark, context switch count, kernel objects in
> use, etc... Thanks. I forgot about VFS nodes.
Xenomai tasks are just Linux tasks, so for all these "metrics", you
should turn to what Linux provides. For the stack high water mark
for instance, I believe neither Linux nor Xenomai have this
information.
--
Gilles.
next prev parent reply other threads:[~2015-01-07 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 16:20 [Xenomai] Resource utilization Mathew Benson
2015-01-07 10:12 ` Gilles Chanteperdrix
2015-01-07 13:06 ` Mathew Benson
2015-01-07 14:06 ` Gilles Chanteperdrix [this message]
2015-01-07 14:30 ` Mathew Benson
2015-01-07 16:20 ` Gilles Chanteperdrix
2015-01-07 17:52 ` Mathew Benson
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=20150107140651.GA10298@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=mathew.benson@gmail.com \
--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.