Opened 22 years ago
Closed 21 years ago
#527 closed defect (wontfix)
See if integrating the smp LFS-Hint has enough of a benefit
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Book | Version: | CVS |
| Severity: | normal | Keywords: | |
| Cc: |
Description
There's always the drawback that more RAM is needed to do parallell builds on single CPU machines. Before we make this part of the normal installation instructions we should do some thorough research and see what is really needed to make it work properly.
Change History (7)
comment:1 by , 21 years ago
comment:2 by , 21 years ago
I have SMP here and have learnt a few SMP tricks along the way. I don't think this is a good idea for the book. Maybe a small mention somewhere, but definitely not adjusting every set of build commands with a variable or whatever. This is more in the realm of "advanced" LFS and is perfectly suited to stay as a hint IMHO.
comment:3 by , 21 years ago
Ok then. Let's add a note somehwere if appropriate and leave it at that.
comment:4 by , 21 years ago
| Priority: | lowest → low |
|---|
comment:5 by , 21 years ago
Actually, the current "parallel compiling" hint looks to be very outdated. Maybe it's not worth mentioning in the book at all.
If we do decide to add a pointer, the 2 locations that stand out are:
1) In the SBU's section where we make mention of SMP 2) In the intro to Ch 6 where we warn against compiling multiple packages in parallel.
comment:6 by , 21 years ago
If that hint is indeed outdated, I don't see the point in adding it. I recommend close this bug, maybe deal with it some other day.
The hint now renamed to parallel compiling. http://cvs.linuxfromscratch.org/index.cgi/hints/parallelcompiling.txt?rev=1.1&content-type=text/x-cvsweb-markup&sortby=date (at time of writing it is not yet in the nightly extract dir)
The book can default $CC_PARALLEL to 1 or MAYBE 2. The amount of ram to run 2 processes in parallel is fairly limited (we're not compiling kde fortunately ;-) ) I guess a machine with 128MB will not see a problem. Off course this all can be written in a bit of explanation :)