archive mirror
 help / color / mirror / Atom feed
From: Yumiko Sugita <>
Subject: Re: [Lkst-develop] Re: Release of LKST 1.3
Date: Thu, 26 Sep 2002 21:36:52 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hello, Robert

   Thank you for your inquiry. I apologize for the delay in replying.

   Let me first explain the background of our development work.
   We began development of the Linux Kernel State Tracer (LKST)
in response to a domestic need to improve Reliability, Availability,
and Serviceability (RAS) with respect to enterprise systems.
The following requirements were applied to LKST:

   * Capable of handling a variety of information about system errors.
   * Little trace overhead (or To control trace overhead)
   * Short development time

   As we had to achieve a short development time, we elected to
develop LKST using our own methodology (based on know-how of
tracer development that we carried out for other OS's) different
from other known tools such as LTT.
# This is not to say that we developed all functions on our own.
#LKST at present connects with Kernel Hooks (GKHI) and LKCD.

   Consequently, LKST, which is oriented to enterprise systems,
has the following features different from those of LTT.
# These LKST features are also being enhanced at this time.

(1) Little overhead and good scalability when tracing on a large-scale
    SMP system
   * To make lock mechanism overhead as little as possible, we
      designed that the buffers are not shared among CPUs.

(2) Easy to extend/expand the function (User-based extendibility)
   * Without recompiling kernel, user can change/add/modify the kind
     of events and information to be recorded at anytime.
      For example, LKST usually traces very few events for the purpose
    of good performance.  Once the kernel get into the particular status
    that user specified, LKST will trace and record more detail information.

(3) Preservation of trace information
   * Recovery of trace information collected at the time of a system crash
     in connection with LKCD.
   * Saving of specific event information during tracing.
      For example, switching to another buffer after the occurrence of
     a specific event enables the information on that event to be left
     in the previous buffer.

(4) Collection of even more kernel event information
   * Information on more than 50 kernel events can be collected for
     kernel debugging.

  The demand for RAS functions in Linux should grow in the years to come.
It is our hope that LKST becomes one means of implementing such functions.

Best regards,
  Yumiko Sugita
  Hitachi,Ltd., Systems Development Laboratory

At 07:58 02/09/19 +0200, Robert Schwebel wrote:
>On Wed, Sep 18, 2002 at 09:20:55PM +0900, Yumiko Sugita wrote:
> > I'd like to announce publication of Linux Kernel State Tracer (LKST)
> > 1.3, which is a tracer for Linux kernel.
>Can you tell us what's the difference between this and the Linux Trace
>Toolkit (LTT)?
>  Dipl.-Ing. Robert Schwebel |
>  Pengutronix - Linux Solutions for Science and Industry
>    Braunschweiger Str. 79,  31134 Hildesheim, Germany
>    Handelsregister:  Amtsgericht Hildesheim, HRA 2686
>     Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4
>Lkst-develop mailing list

  reply	other threads:[~2002-09-26 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 12:20 Release of LKST 1.3 Yumiko Sugita
2002-09-19  5:58 ` Robert Schwebel
2002-09-26 12:36   ` Yumiko Sugita [this message]
2002-09-27 15:48     ` [Lkst-develop] " Karim Yaghmour
2002-10-03  9:46       ` Yumiko Sugita
2002-10-09 18:05         ` Karim Yaghmour
2002-09-19  8:18 ` Vamsi Krishna S.

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to= \ \ \ \ \

* 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 NNTP newsgroup(s).