From: Ingo Molnar <mingo@elte.hu>
To: Mark Knecht <markknecht@gmail.com>
Cc: chaosite@gmail.com, Daniel Walker <dwalker@mvista.com>,
linux-kernel@vger.kernel.org, Lee Revell <rlrevell@joe-job.com>
Subject: Re: Latency data - 2.6.14-rc3-rt13
Date: Tue, 11 Oct 2005 08:14:20 +0200 [thread overview]
Message-ID: <20051011061420.GA20074@elte.hu> (raw)
In-Reply-To: <5bdc1c8b0510102145k3b05c00dm8e3e770c5eee2ee4@mail.gmail.com>
* Mark Knecht <markknecht@gmail.com> wrote:
> Anyway, these latencies seem understood at this point. They are just
> the timer that you set in the kernel hacking section. No big deal.
> However, none of the messages yet give any clues (that I understand)
> as to the cause of the timing misses I'm seeing with 2.6.14-rc3-rt13.
> I shall look into a 2.6.14-rc4-rtX tomorrow.
do you have 64-bit userspace too? If you have 32-bit userspace then
could you try running the x86 kernel? Generally the 64-bit kernel has
less mature debugging options in the -rt tree: e.g. latency tracing
itself doesnt work (due to gcc silliness).
Ingo
next prev parent reply other threads:[~2005-10-11 6:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 20:16 Latency data - 2.6.14-rc3-rt13 Mark Knecht
2005-10-10 20:49 ` Daniel Walker
2005-10-10 21:12 ` Mark Knecht
2005-10-10 21:28 ` Mark Knecht
2005-10-10 21:44 ` Daniel Walker
2005-10-10 22:09 ` Mark Knecht
2005-10-10 22:28 ` Daniel Walker
2005-10-10 23:33 ` Mark Knecht
2005-10-10 23:49 ` Mark Knecht
2005-10-11 3:45 ` Mark Knecht
2005-10-11 6:46 ` Steven Rostedt
2005-10-11 8:56 ` Sven-Thorsten Dietrich
2005-10-11 11:17 ` Ingo Molnar
2005-10-11 22:45 ` Mark Knecht
2005-10-12 0:02 ` Lee Revell
2005-10-12 1:09 ` Mark Knecht
2005-10-12 1:21 ` Lee Revell
2005-10-12 1:25 ` Mark Knecht
2005-10-12 6:38 ` Steven Rostedt
2005-10-12 16:18 ` Lee Revell
2005-10-12 17:03 ` Steven Rostedt
2005-10-11 3:56 ` Matan Peled
2005-10-11 4:45 ` Mark Knecht
2005-10-11 6:14 ` Ingo Molnar [this message]
2005-10-11 7:53 ` Ingo Molnar
2005-10-10 21:39 ` Daniel Walker
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=20051011061420.GA20074@elte.hu \
--to=mingo@elte.hu \
--cc=chaosite@gmail.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=rlrevell@joe-job.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 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.