From: Andrea Arcangeli <andrea@suse.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>, linux-kernel@vger.kernel.org
Subject: Re: KLive: Linux Kernel Live Usage Monitor
Date: Wed, 31 Aug 2005 03:49:06 +0200 [thread overview]
Message-ID: <20050831014906.GO8515@g5.random> (raw)
In-Reply-To: <4314D98E.2030801@tmr.com>
On Tue, Aug 30, 2005 at 06:11:26PM -0400, Bill Davidsen wrote:
> the system, like load. A week running while I was on vacation doesn't
> test much, a week running on a loaded server tests other things.
btw, I thought about adding the load average too but it wasn't really
interesting, since sometime a server is stressed a lot for a few minutes
and then goes back to idle mode. A kernel bug will not necessairly
trigger because some app is I/O bound all the time. Certainly more load
is a factor that increases the probability of bugs and race conditions
though, it's just not obvious how to assign a 0/100% score to a certain
KLive "session".
> The use will depend on how easy it is to install, patch and build isn't
> easy. Crontab is. And I bet developers would be interested in how long
crontab really is easy and standard, crontab seems actually the only way I
could really write the few liner autoinstall script.
next prev parent reply other threads:[~2005-08-31 1:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 3:09 KLive: Linux Kernel Live Usage Monitor Andrea Arcangeli
2005-08-30 8:01 ` Sven Ladegast
2005-08-30 8:29 ` Rogier Wolff
2005-08-30 8:53 ` Sven Ladegast
2005-08-30 9:40 ` Rogier Wolff
2005-08-30 9:54 ` Bernd Petrovitsch
2005-08-30 15:10 ` Andrea Arcangeli
2005-08-30 16:33 ` Alan Cox
2005-08-30 16:16 ` Andrea Arcangeli
2005-08-30 16:56 ` Alan Cox
2005-08-30 16:40 ` Andrea Arcangeli
2005-08-31 18:32 ` Pavel Machek
2005-09-01 15:19 ` Andrea Arcangeli
2005-08-30 16:36 ` Jesper Juhl
2005-08-30 22:11 ` Bill Davidsen
2005-08-31 1:49 ` Andrea Arcangeli [this message]
2005-08-31 19:14 ` tony.luck
2005-08-31 19:47 ` Andrea Arcangeli
2005-09-05 18:26 ` Andrea Arcangeli
2005-08-30 14:45 ` Andrea Arcangeli
2005-08-30 14:36 ` Alan Cox
2005-08-30 22:43 ` Sven Ladegast
2005-08-30 23:25 ` Alan Cox
2005-08-30 23:19 ` Sven Ladegast
2005-08-31 13:34 ` Alan Cox
2005-08-31 14:28 ` Sven Ladegast
2005-08-31 21:23 ` Andrea Arcangeli
2005-08-30 14:56 ` Andrea Arcangeli
2005-08-31 18:20 ` Pavel Machek
2005-09-01 15:23 ` Andrea Arcangeli
2005-09-01 12:26 ` Sven Ladegast
2005-09-05 22:05 ` Marc Giger
2005-09-05 23:13 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2005-08-30 17:08 Wilkerson, Bryan P
2005-08-30 17:44 ` linux-os (Dick Johnson)
2005-08-30 20:31 ` Andrea Arcangeli
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=20050831014906.GO8515@g5.random \
--to=andrea@suse.de \
--cc=R.E.Wolff@BitWizard.nl \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox