Re: lockf in installworld -- not a good idea
- From: Ruslan Ermilov <ru@xxxxxxxxxxx>
- Date: Fri, 29 Sep 2006 22:20:53 +0400
On Fri, Sep 29, 2006 at 11:09:42AM -0600, M. Warner Losh wrote:
[...]
I tend to agree with that basic philosophy. From other items in theThey are safe to do nowadays. I'll do some measurements on real
thread, it was clear this came up in the context of build release,
which benefits from -j usually. The installworld phase in that should
be as robust as possible as well, since otherwise we have issues with
the actual release. Unless it is a big win (more than a few percent),
I'd imagine the right fix is to the release target to not do a
parallel installworld. I know that in the build scripts that I wrote
in 3.x days and have ported forward since then I've never done a
parallel install, due to it rarely working reliably in that (long)
time span...
SMP with the memory-based DESTDIR, and let you know the numbers.
Cheers,
--
Ruslan Ermilov
ru@xxxxxxxxxxx
FreeBSD committer
Attachment:
pgptTbzLNOMsH.pgp
Description: PGP signature
- Follow-Ups:
- Re: lockf in installworld -- not a good idea
- From: Ruslan Ermilov
- Re: lockf in installworld -- not a good idea
- From: Astrodog
- Re: lockf in installworld -- not a good idea
- References:
- Re: lockf in installworld -- not a good idea
- From: Astrodog
- Re: lockf in installworld -- not a good idea
- From: Warner Losh
- Re: lockf in installworld -- not a good idea
- From: Robert Watson
- Re: lockf in installworld -- not a good idea
- From: M. Warner Losh
- Re: lockf in installworld -- not a good idea
- Prev by Date: Re: Some interesting plots
- Next by Date: Re: lockf in installworld -- not a good idea
- Previous by thread: Re: lockf in installworld -- not a good idea
- Next by thread: Re: lockf in installworld -- not a good idea
- Index(es):