From: Kees Cook <keescook@chromium.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Kees Cook <keescook@chromium.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] docs, parallelism: Rearrange how jobserver reservations are made
Date: Wed, 20 Nov 2019 16:03:01 -0800 [thread overview]
Message-ID: <20191121000304.48829-1-keescook@chromium.org> (raw)
Hi,
As Rasmus noted[1], there were some deficiencies in how the Make jobserver
vs sphinx parallelism logic was handled. This series attempts to address
all those problems by building a set of wrappers and fixing some of the
internal logic.
Thank you Rasmus for the suggestions (and the "jobhog" example)! :)
-Kees
[1] https://lore.kernel.org/lkml/eb25959a-9ec4-3530-2031-d9d716b40b20@rasmusvillemoes.dk
Kees Cook (3):
docs, parallelism: Fix failure path and add comment
docs, parallelism: Do not leak blocking mode to writer
docs, parallelism: Rearrange how jobserver reservations are made
Documentation/Makefile | 5 +-
Documentation/sphinx/parallel-wrapper.sh | 25 +++++++++
scripts/jobserver-count | 58 --------------------
scripts/jobserver-exec | 69 ++++++++++++++++++++++++
4 files changed, 96 insertions(+), 61 deletions(-)
create mode 100644 Documentation/sphinx/parallel-wrapper.sh
delete mode 100755 scripts/jobserver-count
create mode 100644 scripts/jobserver-exec
--
2.17.1
next reply other threads:[~2019-11-21 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 0:03 Kees Cook [this message]
2019-11-21 0:03 ` [PATCH 1/3] docs, parallelism: Fix failure path and add comment Kees Cook
2019-11-21 0:03 ` [PATCH 2/3] docs, parallelism: Do not leak blocking mode to writer Kees Cook
2019-11-21 7:41 ` Rasmus Villemoes
2019-11-21 19:09 ` Kees Cook
2019-11-21 0:03 ` [PATCH 3/3] docs, parallelism: Rearrange how jobserver reservations are made Kees Cook
2019-11-21 8:09 ` Rasmus Villemoes
2019-11-21 19:39 ` Kees Cook
2019-11-21 19:52 ` Kees Cook
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=20191121000304.48829-1-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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;
as well as URLs for NNTP newsgroup(s).