linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: Richard J Moore <richardj_moore@uk.ibm.com>
Cc: John Levon <movement@marcelothewonderpenguin.com>,
	Andrew Morton <akpm@zip.com.au>,
	Andrea Arcangeli <andrea@suse.de>, bob <bob@watson.ibm.com>,
	linux-kernel@vger.kernel.org,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	mjbligh@linux.ibm.com, John Levon <moz@compsoc.man.ac.uk>,
	Rik van Riel <riel@conectiva.com.br>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Enhanced profiling support (was Re: vm lock contention reduction)
Date: Wed, 10 Jul 2002 16:30:42 -0400	[thread overview]
Message-ID: <3D2C9972.BB3DA772@opersys.com> (raw)
In-Reply-To: <OFF41DACAC.FEED90BA-ON80256BF2.004DC147@portsmouth.uk.ibm.com>

Richard J Moore wrote:
> Some level of tracing (along with other complementary PD tools e.g. crash
> dump) needs to be readiliy available to deal with those types of problem we
> see with mature systems employed in the production environment. Typically
> such problems are not readily recreatable nor even prictable. I've often
> had to solve problems which impact a business environment severely, where
> one server out of 2000 gets hit each day, but its a different one each day.
> Its under those circumstances that trace along without other automated data
> capturing problem determination tools become invaluable. And its a fact of
> life that only those types of difficult problem remain once we've beaten a
> system to death in developments and test. Being able to use a common set of
> tools whatever the componets under investigation greatly eases problem
> determination. This is especially so where you have the ability to use
> dprobes with LTT to provide ad hoc tracepoints that were not originally
> included by the developers.

I definitely agree.

One case which perfectly illustrates how extreme these situations can be is
the Mars Pathfinder. The folks at the Jet Propulsion Lab used a tracing tool
very similar to LTT to locate the priority inversion problem the Pathfinder
had while it was on Mars.

The full account gives an interesting read (sorry for the link being on
MS's website but its author works for MS research ...):
http://research.microsoft.com/research/os/mbj/Mars_Pathfinder/Authoritative_Account.html

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-07-10 20:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 14:28 Richard J Moore
2002-07-10 20:30 ` Karim Yaghmour [this message]
2002-07-10 21:41   ` Andrea Arcangeli
2002-07-11  4:47     ` Karim Yaghmour
2002-07-11  4:59       ` Karim Yaghmour
  -- strict thread matches above, loose matches on Subject: below --
2002-07-07  2:50 vm lock contention reduction Andrew Morton
2002-07-07  3:05 ` Linus Torvalds
2002-07-07  3:47   ` Andrew Morton
2002-07-08 11:39     ` Enhanced profiling support (was Re: vm lock contention reduction) John Levon
2002-07-08 17:52       ` Linus Torvalds
2002-07-08 18:41         ` Karim Yaghmour
2002-07-10  2:22           ` John Levon
2002-07-10  4:16             ` Karim Yaghmour
2002-07-10  4:38               ` John Levon
2002-07-10  5:46                 ` Karim Yaghmour
2002-07-10 13:10                 ` bob

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=3D2C9972.BB3DA772@opersys.com \
    --to=karim@opersys.com \
    --cc=akpm@zip.com.au \
    --cc=andrea@suse.de \
    --cc=bob@watson.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mjbligh@linux.ibm.com \
    --cc=movement@marcelothewonderpenguin.com \
    --cc=moz@compsoc.man.ac.uk \
    --cc=richardj_moore@uk.ibm.com \
    --cc=riel@conectiva.com.br \
    --cc=torvalds@transmeta.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