mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] docs: net: 80211: reduce docs build time
Date: Thu, 08 Oct 2020 10:42:29 +0200	[thread overview]
Message-ID: <81ebd41b4f39c78867949e6453b2fb58e69ed48d.camel@sipsolutions.net> (raw)
In-Reply-To: <f0085721d85ebc3a77164b457ed948eee48b55df.1601890703.git.mchehab+huawei@kernel.org>

On Mon, 2020-10-05 at 11:38 +0200, Mauro Carvalho Chehab wrote:
> the files under /80211 calls kernel-doc script 207 times, one for each
> single function and doc chapter. Due to that, it takes a lot of time
> handling it:
> 
> 	$ touch Documentation/driver-api/80211/*rst && time make SPHINXDIRS=driver-api/80211 htmldocs
> ...
> 	real	0m22,928s
> 	user	0m21,644s
> 	sys	0m1,334s
> 
> Reduce the build time by doing only one kernel-doc call
> per functions that belong to the same group. With that, there's now
> 50 calls to kernel-doc, which makes the build time for those docs
> 62% faster:
> 
> 	$ touch Documentation/driver-api/80211/*rst && time make SPHINXDIRS=driver-api/80211 htmldocs
> ...
> 	real	0m8,666s
> 	user	0m8,084s
> 	sys	0m0,642s
> 
> As a side effect, it should now be easier to add newer
> functions, as there's no need to repeat the kernel-doc
> pattern.

Thanks, I'll apply this.

I wasn't even aware of that syntax ...

johannes


      reply	other threads:[~2020-10-08  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05  9:38 Mauro Carvalho Chehab
2020-10-08  8:42 ` Johannes Berg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81ebd41b4f39c78867949e6453b2fb58e69ed48d.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®