From: Andrea Arcangeli <andrea@cpushare.com>
To: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Linux 2.6.15.2
Date: Tue, 7 Feb 2006 16:55:11 +0100 [thread overview]
Message-ID: <20060207155511.GD21873@opteron.random> (raw)
In-Reply-To: <19210076647.20060131153123@dns.toxicfilms.tv>
On Tue, Jan 31, 2006 at 03:31:23PM +0100, Maciej Soltysiak wrote:
> Andrea Arcangeli's klive could some day be a measure of the bug-affected
> fraction. If it already is not. Klive reports hardware setups
> and configuration. I am not sure if it is available somehow but
> maybe it would be nice to query klive database in an SQL manner?
>
> > SELECT COUNT(*) from hosts WHERE kernel = "2.6.15" and config_scsi = 'y'
> and ...;
> > 3089
The problem of querying with sql is just a matter of security. You can
build complex queries that may turn off a db server (I learnt the hard
way what happens with LIKE '%% preemptive %%', for whatever reason pgsql
has an heuristic that assumes long strings will be very selective in
LIKE statements and they will return very little results, but of course
it's impossible to predict that without analyzing the dataset too, in
the preemptive case lots of data is returned...).
If there's demand for the above, I'd rather prefer to export the whole
sql database and to upload it on ftp.kernel.org, so you can import it
with psql -i. So you can import it locally and run your queries and
stats locally (anonymously too). I know this is less handy than querying
on the web, but unless you've a spare crashable box to offer, I'm not
willing to put my server at risk (also given I've commercial
applications running on it and not only KLive ;).
The KLive data is meant to be public. The website publishes most of it
already in a handy browsable form. The only thing that is private are
the ip addresses, and those should be filtered out before exporting.
next prev parent reply other threads:[~2006-02-07 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 14:31 Linux 2.6.15.2 Maciej Soltysiak
2006-02-07 15:55 ` Andrea Arcangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-31 7:06 Greg KH
2006-01-31 7:07 ` Greg KH
2006-01-31 7:34 ` Andrew Morton
2006-01-31 7:38 ` Greg KH
2006-01-31 7:44 ` Andrew Morton
2006-01-31 17:43 ` Greg KH
2006-01-31 13:04 ` Steven Rostedt
2006-02-03 12:09 ` Holger Eitzenberger
2006-02-03 19:14 ` Andrew Morton
2006-02-04 11:52 ` Holger Eitzenberger
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=20060207155511.GD21873@opteron.random \
--to=andrea@cpushare.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=solt2@dns.toxicfilms.tv \
/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