Re: [PATCH 2/2] pack-objects: Default to zero threads, meaning auto-assign to #cpus
- From
Nicolas Pitre <nico@cam.org>
- Date
- Feb 12, 2008, 04:57 UTC
- Message-ID
- <alpine.LFD.1.00.0802112352380.2732@xanadu.home>
- In-Reply-To
- <47B10B7D.2030702@nrlssc.navy.mil>
On Mon, 11 Feb 2008, Brandon Casey wrote:
Show 5 quoted lines
> Additionally, update some tests for which the multi-threaded result > differs from the single-threaded result and the single-threaded > result is expected. > > Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
I think the first patch is OK, but having the _default_ be multi-threaded is going a bit too far. IMHO you should document the meaning of the value 0, and compile with thread support whenever Posix threads are available, but activating threads should be done explicitly.
Nicolas