From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] download/git: re-run the backend with a lock to the git tree
Date: Mon, 10 Sep 2018 22:52:28 +0200 [thread overview]
Message-ID: <20180910225228.56cdb555@windsurf> (raw)
In-Reply-To: <b5a3123305e1d4cef3cbdb17985e73161d13f407.1534972250.git.yann.morin.1998@free.fr>
Hello,
+Arnout.
On Wed, 22 Aug 2018 23:10:55 +0200, Yann E. MORIN wrote:
> The access-pattern to the git repository must be entirely atomic.
>
> This atomicity is currently guaranteed by the caller, from a higher
> level. But this is not optimum, and it is better that the backend does
> the locking it needs by itself, so that other backends from other builds
> can still download for the same package (e.g. another build uses a wget
> download for that package).
I'd like to challenge the complexity vs. benefit of this patch and
PATCH 3/5. Basically, you replace a single $(FLOCK) call in dl-wrapper,
by 30 additional lines in the git-specific wrapper (including a
non-trivial trick that consists in calling itself), for a benefit that
is very, very limited. A download of the exact same package, from
another download method, happening at the same time. Can occur yes, but
is it really worth the additional complexity? I doubt it.
So at this point, I am not really enthusiastic about 2/5 and 3/5, but
perhaps you'll have some convincing arguments ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-10 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 21:10 [Buildroot] [PATCH 0/5] download: add a timeout and use a more fine-grained locking heuristic Yann E. MORIN
2018-08-22 21:10 ` [Buildroot] [PATCH 1/5] download/git: fix code-style Yann E. MORIN
2018-09-10 20:44 ` Thomas Petazzoni
2018-08-22 21:10 ` [Buildroot] [PATCH 2/5] download/git: re-run the backend with a lock to the git tree Yann E. MORIN
2018-09-10 20:52 ` Thomas Petazzoni [this message]
2018-10-14 12:54 ` Yann E. MORIN
2018-10-20 22:11 ` Arnout Vandecappelle
2018-10-22 21:12 ` Yann E. MORIN
2018-10-22 22:11 ` Arnout Vandecappelle
2018-08-22 21:10 ` [Buildroot] [PATCH 3/5] download: move locking into download wrapper Yann E. MORIN
2018-08-22 21:10 ` [Buildroot] [PATCH 4/5] core/download: add per-download timeout Yann E. MORIN
2018-09-10 20:55 ` Thomas Petazzoni
2018-10-14 13:07 ` Yann E. MORIN
2018-10-20 21:49 ` Arnout Vandecappelle
2018-08-22 21:10 ` [Buildroot] [PATCH 5/5] utils/genrandconfig: add a 30-minute timeout Yann E. MORIN
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=20180910225228.56cdb555@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.