Re: [PATCH] perf: Move fs.* to generic lib/lk/

[Borislav Petkov <bp@alien8.de>]

On Thu, Nov 21, 2013 at 12:17:44PM +0100, Ingo Molnar wrote:
> > However, now that I think of it, the naming is kinda imprecise 
> > having only "kernel" in it - it only denotes that it is a library of 
> > stuff that has grown in the kernel.
> > 
> > So how about
> > 
> > tools/lib/ktools/
> > tools/lib/kutils/
> > tools/lib/kernel-tools/
> > tools/lib/kernel-utils/
> > ...
> > 
> > and
> > 
> > libktools.so
> > libkutils.so
> > ...
> > 
> > ?
> > 
> > I'd prefer ktools as in the tools/ directory of the kernel repo.
> 
> So what does each name mean, what would they be used for and what's 
> the difference between them?

Oh no, I'm only proposing multiple libraries but multiple names to
choose *only* *one* from them - the one which we think fits best.

Basically I wanna say: "this is the library of tools which grew in the
tools/ directory of the kernel repo".

Thus I'm proposing

	tools/lib/ktools/

as a path and

	libktools.so

as a library name, because, IMHO, this name is closer to the reality.

tools/lib/kernel/ is also ok - it does not describe the collection of
functionality that precisely, IMHO, that's all.

Am I even making sense here?

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--