From: Andi Kleen <andi@firstfloor.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [patch 1/4] KMON - kmon device/instrumentation ...
Date: 10 May 2007 15:23:50 +0200 [thread overview]
Message-ID: <p73k5vgg6c9.fsf@bingen.suse.de> (raw)
In-Reply-To: <send-serie.davidel@xmailserver.org.27461.1178495355.1>
Davide Libenzi <davidel@xmailserver.org> writes:
> This patch serie introduces a way to log high frequency/volume data
> out of the kernel. Logging scheduler operations for example, with
> loads that generate tenths of thousands of context switches per second
> (possibly from multiple CPUs), can overload the kernel printk. Also,
> logging in binary form helps in reducing the size of the logged data
> that is tranfered from kernel to userspace. The kmon logger uses per
> CPU buffers (rings) that are flushed at a given frequency to all the
> instances of the kmon devices.
Sounds like you reinvented relayfs? (and ktrace before that)
-Andi
next prev parent reply other threads:[~2007-05-10 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 23:49 [patch 1/4] KMON - kmon device/instrumentation Davide Libenzi
2007-05-10 13:23 ` Andi Kleen [this message]
2007-05-10 15:22 ` Davide Libenzi
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=p73k5vgg6c9.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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