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

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: <20131127154255.GJ32267@pd.tnic>
Date:	Wed, 27 Nov 2013 16:42:55 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Arnaldo Carvalho de Melo <acme@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Borislav Petkov <bp@...e.de>, Jiri Olsa <jolsa@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Robert Richter <rric@...nel.org>
Subject: Re: [PATCH] perf: Move fs.* to generic lib/lk/

On Tue, Nov 26, 2013 at 07:03:33PM +0100, Ingo Molnar wrote:
> Not necessarily, if the number goes up - obviously then we'd also want
> to add some second directory structure to organize them into broad
> categories or so.

Right, topic libraries. That is starting to make more sense. :)

> Unnecessarily longer build time.

Ok.

> If a tool uses just a handful of these (hopefully quickly increasing
> number of) facilities then it should not be burdened by building it
> all.

Ok. This still hints at topic libraries as being the best alternative.

> The preprocessor does nothing with the .a - eliminating extra stuff
> from the .a is a link time step, and that means the whole .a will be
> built first ...

Ok, this is an argument I can get on board with.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/