From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: ksummit-2012-discuss@lists.linux-foundation.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2012-discuss] [ATTEND or not ATTEND] That's the question!
Date: Sat, 16 Jun 2012 15:56:03 +0200 [thread overview]
Message-ID: <201206161556.03410.rjw@sisk.pl> (raw)
In-Reply-To: <20120616072906.7469ec24@tpl.lwn.net>
On Saturday, June 16, 2012, Jonathan Corbet wrote:
> On Sat, 16 Jun 2012 12:50:05 +0200 (CEST)
> Thomas Gleixner <tglx@linutronix.de> wrote:
>
> > A good start would be if you could convert your kernel statistics into
> > accounting the consolidation effects of contributions instead of
> > fostering the idiocy that corporates have started to measure themself
> > and the performance of their employees (I'm not kidding, it's the sad
> > reality) with line and commit count statistics.
>
> I would dearly love to come up with a way to measure "real work" in
> some fashion; I've just not, yet, figured out how to do that. I do
> fear that the simple numbers we're able to generate end up creating the
> wrong kinds of incentives.
I have exactly the same feeling about that.
> Any thoughts on how to measure "consolidation effects"? I toss out
> numbers on code removal sometimes, but that turns out to not be a whole
> lot more useful than anything else on its own.
Well, that is very difficult to measure. I'd look for cases in which certain
function calls and data types become more widespread.
next prev parent reply other threads:[~2012-06-16 13:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 22:56 [ATTEND or not ATTEND] That's the question! Thomas Gleixner
2012-06-15 23:34 ` [Ksummit-2012-discuss] " Greg KH
2012-06-16 10:50 ` Thomas Gleixner
2012-06-16 13:29 ` Jonathan Corbet
2012-06-16 13:32 ` Frederic Weisbecker
2012-06-16 13:56 ` Rafael J. Wysocki [this message]
2012-06-17 10:40 ` Thomas Gleixner
2012-06-17 18:51 ` Greg KH
2012-06-17 18:58 ` Mark Brown
2012-06-20 19:51 ` J. Bruce Fields
2012-07-06 9:43 ` Glauber Costa
2012-07-06 9:54 ` Frederic Weisbecker
2012-07-06 9:59 ` Glauber Costa
2012-07-06 10:00 ` Srivatsa S. Bhat
2012-07-06 10:03 ` Glauber Costa
2012-07-06 10:21 ` Srivatsa S. Bhat
2012-07-06 10:11 ` Richard Cochran
2012-07-06 10:14 ` Glauber Costa
2012-07-06 10:36 ` Srivatsa S. Bhat
2012-07-06 10:43 ` Glauber Costa
2012-07-06 12:42 ` Steven Rostedt
2012-07-17 22:17 ` david
2012-06-16 11:30 ` Alan Cox
2012-06-16 15:03 ` Phil Turmel
2012-06-16 16:43 ` Myklebust, Trond
2012-06-20 0:40 ` Dave Chinner
2012-06-17 17:04 ` Mark Brown
2012-06-19 15:45 ` Bjorn Helgaas
2012-06-19 19:18 ` Roland Dreier
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=201206161556.03410.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=corbet@lwn.net \
--cc=ksummit-2012-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.