Re: [TECH TOPIC] Kernel documentation - update and future directions

[Randy Dunlap <rdunlap@infradead.org>]

Hi,

On 9/1/25 10:52 AM, Mark Brown wrote:
> On Mon, Sep 01, 2025 at 09:51:01AM -0700, Randy Dunlap wrote:
> 
>> Willy had a suggestion that we just make checking kernel-doc during
>> all .c builds a permanent feature instead of a W=1 option.
>> This helps, but still doesn't force 'make htmldocs' to be run.
> 
> make htmldocs is rather slow:
> 
>   $ time make -j56 htmldocs
>   ...
>   make -j56 htmldocs  2355.99s user 141.33s system 158% cpu 26:14.86 total

Wow. I just ran 'make -j8 htmldocs' on my 16 GB intel core-i7 laptop:

1205.85user 66.15system 6:05.82elapsed 347%CPU (0avgtext+0avgdata 1298044maxresident)k
697432inputs+1128016outputs (92major+16863601minor)pagefaults 0swaps

(using /usr/bin/time)

How much RAM does your build system have?

> 
> and produces a bunch of warnings with current mainline it seems.  That
> compares unfavourably with allmodconfig on this system:
> 
>   $ time make -j56 allmodconfig
>   ...
>   make -j56 allmodconfig  5.31s user 1.93s system 146% cpu 4.931 total
>   $ time make -j56
>   ...
>   make -j56  53468.11s user 4387.30s system 5084% cpu 18:57.77 total

whereas my x86_64 allmodconfig build takes over 1 hour.  :(

> and seems rather more likely to flag something for me.

OK, good to hear. Thanks.

-- 
~Randy