linux-kernel - Re: [PATCH 0000/2297] [ANNOUNCE, RFC] "Fast Kernel Headers" Tree -v1: Eliminate the Linux kernel's "Dependency Hell"

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAHp75VeUmg73d6gua+LoHiyihMW3tqexTYe4QvKXS8gbXZP15w@mail.gmail.com>
Date:   Wed, 5 Jan 2022 11:37:02 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Ingo Molnar <mingo@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-arch <linux-arch@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        "David S. Miller" <davem@...emloft.net>,
        Ard Biesheuvel <ardb@...nel.org>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Jonathan Corbet <corbet@....net>,
        Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH 0000/2297] [ANNOUNCE, RFC] "Fast Kernel Headers" Tree -v1:
 Eliminate the Linux kernel's "Dependency Hell"

On Wed, Jan 5, 2022 at 4:08 AM Arnd Bergmann <arnd@...db.de> wrote:
> On Mon, Jan 3, 2022 at 6:12 AM Ingo Molnar <mingo@...nel.org> wrote:

...

> Most of the patches should be the same either way (adding back
> missing includes to drivers, and doing cleanups to commonly
> included headers to avoid the deep nesting), the interesting bit
> will be how to properly define the larger structures without pulling
> in the rest of the world.

I'm wondering if the compiler can provide us the statistics of usage
on a per custom type basis. In this case the highest frequency will
probably mean that we better have that type in a separate header or
tree of _independent_ headers.


-- 
With Best Regards,
Andy Shevchenko