mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: sugita <sugita@sdl.hitachi.co.jp>
To: linux-kernel@vger.kernel.org
Cc: lkst-develop@lists.sourceforge.net
Subject: The new function of LKST is released
Date: Tue, 22 Mar 2005 11:02:42 +0900	[thread overview]
Message-ID: <423F7CC2.305883C1@sdl.hitachi.co.jp> (raw)

Dear all,

 We are pleased to announce releasing new function of Linux
Kernel State Tracer(a.k.a. LKST).
 It's a lkstlogtools for analyzing performance of kernel.
This function is released as lkstlogtools v1.0.1.
For using this function, LKST v2.2.1 is needed.
Please use this tool and give us some comment.

---
The development of this program is partly supported by IPA
(Information-Technology Promotion Agency, Japan).
---

 LKST with lkstlogtools can collect the queue information and
the execution time of some key processing and analyze them.
lkstlogtools provides some tools for analyzing and visualizing LKST
data too.
>From these analyzed data, user can know what processing is slow
and the status of the queue at the time.
Thus user can use LKST with lkstlogtools as a tool to evaluate
kernel performance.

---
lkstlogtools and LKST binaries, source code and documents are
available in the following site,
http://sourceforge.net/projects/lkst/
http://sourceforge.jp/projects/lkst/

We prepared a mailing list written below in order to let users know
update of LKST.
 lkst-users@lists.sourceforge.net
 lkst-users@lists.sourceforge.jp

And if you have any comments, please send to the above list, or to
another mailing-list written below.
 lkst-develop@lists.sourceforge.net
 lkst-develop@lists.sourceforge.jp

Best regards,
All of the LKST developers
-----------------
Yumiko Sugita
Hitachi,Ltd., Systems Development Laboratory
E-mail: sugita@sdl.hitachi.co.jp


                 reply	other threads:[~2005-03-22  2:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=423F7CC2.305883C1@sdl.hitachi.co.jp \
    --to=sugita@sdl.hitachi.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkst-develop@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®