From: Simon Glass <sjg@chromium.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Tom Rini <trini@konsulko.com>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH] genboardscfg: limit to 240 jobs
Date: Wed, 12 Jan 2022 13:04:10 -0700 [thread overview]
Message-ID: <CAPnjgZ0j-s=p7ehDsr02yCpZUvcvSqivhzvPg-1r4uXfNUff3A@mail.gmail.com> (raw)
In-Reply-To: <20220111153450.912230-1-andre.przywara@arm.com>
On Tue, 11 Jan 2022 at 08:35, Andre Przywara <andre.przywara@arm.com> wrote:
>
> When genboardscfg.py is run on machines with 255 or more cores, the
> process will consume more than 1024 file descriptors, which is a common
> standard ulimit for user processes. As a consequence it will fail with a
> lenghty Python trace, with the almost hidden message:
> OSError: [Errno 24] Too many open files
>
> It's somewhat questionable whether that level of parallelity is actually
> useful for genboardscfg, so we limit the *default* number of jobs to the
> safe number of 240, to avoid the problem.
> If a user persists, she can still force a higher number via the -j
> parameter - hopefully having raised the ulimit accordingly beforehand.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> tools/genboardscfg.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Glass <sjg@chromium.org>
Please send such machine. Thank you.
next prev parent reply other threads:[~2022-01-12 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 15:34 [PATCH] genboardscfg: limit to 240 jobs Andre Przywara
2022-01-11 15:48 ` Heinrich Schuchardt
2022-01-12 20:04 ` Simon Glass [this message]
2022-01-13 18:00 ` Simon Glass
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='CAPnjgZ0j-s=p7ehDsr02yCpZUvcvSqivhzvPg-1r4uXfNUff3A@mail.gmail.com' \
--to=sjg@chromium.org \
--cc=andre.przywara@arm.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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.