linux-kernel - Re: [RFC] Create kinst/ or ki/ directory ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.999.0710301044110.30120@woody.linux-foundation.org>
Date:	Tue, 30 Oct 2007 10:50:23 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
cc:	Jeff Garzik <jeff@...zik.org>, Randy Dunlap <rdunlap@...otime.net>,
	hch@...radead.org, linux-kernel@...r.kernel.org,
	Sam Ravnborg <sam@...nborg.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	Prasanna S Panchamukhi <prasanna@...ibm.com>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
	"David S. Miller" <davem@...emloft.net>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <pzijlstr@...hat.com>,
	Philippe Elie <phil.el@...adoo.fr>,
	"William L. Irwin" <wli@...omorphy.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Christoph Lameter <christoph@...eter.com>,
	Valdis.Kletnieks@...edu
Subject: Re: [RFC] Create kinst/ or ki/ directory ?

On Tue, 30 Oct 2007, Mathieu Desnoyers wrote:
>
> * Jeff Garzik (jeff@...zik.org) wrote:
> ...
> > Pick a shorter word like probes or profile or what... or better yet... 
> > just leave most things in their current directories.
> ...
> 
> 
> How about something along the
> 
> kinst or ki
> 
> lines ?
> 
> (for "kernel instrumentation")

No, that's horrible.

Also, in general, why do people want to have an "instrumentation" thing? 
Yes, you can put random things into the same box, but that doesn't make 
them be the same thing. Personally, I don't think "instrumentation" is 
very useful at all. I consider "profiling" and "markers" to be two 
fundamentally different things, and putting them both in the same box does 
not make them any more similar. 

Yes, technically they are both "instrumentation", but hey, technically the 
VM and the VFS layer are both "infrastructure", but we don't put *those* 
in a "infrastructure" subdirectory.

In other words, the fact that two different things share some attribute 
does not mean that they should be collapsed together by that attribute, 
does it?

I think "instrumentation" was/is a particularly bad thing to group things 
by. It doesn't actually tell you anything about the thing, and it's not 
even true that some people are interested in "instrumentation"  and others 
aren't. 

For example: I think profiling support is something REALLY FUNDAMENTAL. 
It's something each and every developer should generally care about, and 
OProfile should be considered an indispensable tool for any developer, on 
par with something like gdb.

In contrast, we should *not* expect most people to do any kernel markers 
etc. That's a very esoteric thing.

So I actually think that the current Kconfig.instrumentation should be 
*removed*. Rather than adding more groupings based on that fundamentally 
flawed premise of false commonality.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/