From: fche@redhat.com (Frank Ch. Eigler)
To: Andrew Morton <akpm@osdl.org>
Cc: Martin Peschke <mp3@de.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] statistics: fix buffer overflow in histogram with linear scale
Date: 20 Oct 2006 17:15:20 -0400 [thread overview]
Message-ID: <y0mpscmvgd3.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <20061020115242.ff4acce2.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> writes:
> So... what are we going to do with the statistics stuff? It needs users
> to prove its desirability/suitability. I think there was some work done in
> the SCSI area - did that come to anything?
There may be an opportunity here for combining this and the
markers-based lttng work. Statistics gathering would be just one of
several possible back-end for events corresponding to scsi quantity
changes: tracing or more elaborate probing would also be enabled.
- FChE
prev parent reply other threads:[~2006-10-20 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 13:58 Martin Peschke
2006-10-20 18:52 ` Andrew Morton
2006-10-20 21:15 ` Frank Ch. Eigler [this message]
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=y0mpscmvgd3.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mp3@de.ibm.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
Powered by JetHome