From: Dave Brolley <brolley@redhat.com>
To: moris dong <moris_dong@hotmail.com>
Cc: sid@sources.redhat.com
Subject: Re: SMP board : Bug in SID or configuration file ?
Date: Tue, 29 Mar 2005 19:21:00 -0000 [thread overview]
Message-ID: <4249AABF.1030505@redhat.com> (raw)
In-Reply-To: <BAY22-F288BFFC2A7BDC7B5A63068F8450@phx.gbl>
Hi! I can comment on your question 2) below....
moris dong wrote:
>
> 2. I want to see how each CPU affects the performance of the other
> (e.g., contention on bus and memory that causes delays and stalls).
> How can I monitor these parameters?
>
We have a port here which had the same requirements and, so we created
some infrastructure in SID for this kind of thing. The port itself,
unfortunately can not be contributed at this time, however, the
infrastructure which allows for modelling of bus contention and stalls
probably can. As usual, my problem is one of time. I'll see what I can
do over the next week or so to get it approved and committed.
Dave
next prev parent reply other threads:[~2005-03-29 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 18:37 moris dong
2005-03-29 19:21 ` Dave Brolley [this message]
2005-03-30 19:04 ` Frank Ch. Eigler
2005-03-31 6:30 ` moris dong
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=4249AABF.1030505@redhat.com \
--to=brolley@redhat.com \
--cc=moris_dong@hotmail.com \
--cc=sid@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).