All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>, Kees Cook <keescook@chromium.org>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: Sphinx parallel build errors
Date: Thu, 10 Oct 2019 13:15:51 -0700	[thread overview]
Message-ID: <c6263597-e9d0-5a1f-effd-d1706c24e666@infradead.org> (raw)
In-Reply-To: <20191010124832.23bc4362@lwn.net>

On 10/10/19 11:48 AM, Jonathan Corbet wrote:
> On Wed, 9 Oct 2019 19:30:56 -0700
> Kees Cook <keescook@chromium.org> wrote:
> 
>> I'm wondering if it's actually the addition of
>> the MAINTAINERS file parsing -- that's a really big parse and maybe that
>> pushed things over the edge?
> 
> That does seem like a likely culprit, doesn't it?  Watching a build here,
> though, I don't see that any one of the sphinx-build processes balloons to
> a horrific size, which is what I would expect if one file were causing the
> problem.
> 
> In general, the sphinx build doesn't really begin to approach the memory
> requirements of, say, firefox or my mail client on my system.
> 
> Randy, I'd be curious to know if you see the same behavior with current
> mainline.  Also, can you see how many sphinx-build processes you have
> running?

Yes, I see oom-kills when building docs for 5.4-rc2.
But only after I ran 'gimp *.jpg' for 22 photos.

I can see anywhere from 1 to 4 sphinx-build processes running.

> Thanks,
> 
> jon

-- 
~Randy

  reply	other threads:[~2019-10-10 20:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 21:37 Sphinx parallel build errors Randy Dunlap
2019-10-09 21:40 ` Jonathan Corbet
2019-10-09 22:18   ` Randy Dunlap
2019-10-10  2:30 ` Kees Cook
2019-10-10  3:00   ` Bhaskar Chowdhury
2019-10-10 18:48   ` Jonathan Corbet
2019-10-10 20:15     ` Randy Dunlap [this message]
2019-10-27 18:11       ` Randy Dunlap
2019-10-27 18:17         ` Jonathan Corbet
2019-10-27 18:30           ` Randy Dunlap
2019-10-27 19:05             ` Mauro Carvalho Chehab
2019-10-27 19:36               ` Randy Dunlap
2019-10-28 19:07               ` Kees Cook
2019-10-29  8:16                 ` Markus Heiser
2019-10-29 16:09                   ` Kees Cook
2019-10-29 19:41                   ` Randy Dunlap
2019-10-29 19:57                     ` Markus Heiser
2019-10-29 20:10                       ` Randy Dunlap

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=c6263597-e9d0-5a1f-effd-d1706c24e666@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.