All of lore.kernel.org
 help / color / mirror / Atom feed
From: vanandel@ucar.edu
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: karim@opersys.com, LTT-Dev <ltt-dev@shafik.org>
Subject: please include LTT in the Linux kernel
Date: Tue, 05 Nov 2002 21:33:01 -0700	[thread overview]
Message-ID: <3DC89B7D.6000802@ucar.edu> (raw)
In-Reply-To: 3DC727CD.96EE29AE@opersys.com

Karim Yaghmour wrote:
> Apparently Linus doesn't see what this patch buys Linux. Since
> I can't personally convince him otherwise, having written LTT
> myself, here it is in the hope that others on the list actually
> find it of some use.

I am quite interested in having LTT as a configurable option in the 
Linux kernel.  My company (the National Center for Atmospheric Research) 
uses networks of Linux computers to process data from weather radars. 
Occasionally, we've had unexplained performance problems where the 
system is slow to respond, even though the process load is low on each 
computer and no process is "hogging" the CPU.  LTT would be extremely 
valuable to help us diagnose such problems, since we could see the 
interaction of our processing and radar display tasks with the kernel 
and the NFS daemons.

Also, we build Linux based data acquisition systems containing signal 
processing cards.  LTT would really help us tune the performance of 
these systems, since we could see how quickly our processes are 
scheduled in response to interrupts from the signal processing cards.

Please, include LTT in the Linux kernel.  Karim and others have 
demonstrated that LTT has no impact on kernel performance if it is not 
configured, and minimal impact even when tracing is enabled.  I've used 
a commercial product (Stethoscope - sold by Real Time Innovations) when 
doing real-time programming on VxWorks, and found it quite valuable.  If 
LTT is included in the Linux kernel, Linux will be much more appealing 
to the real-time and embedded programming community.




      parent reply	other threads:[~2002-11-06  4:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05  2:07 [PATCH] LTT for 2.5.46 1/10: Core definitions Karim Yaghmour
2002-11-05  2:51 ` Skip Ford
2002-11-06  4:33 ` vanandel [this message]

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=3DC89B7D.6000802@ucar.edu \
    --to=vanandel@ucar.edu \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.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.