git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] autodetect number of CPUs by default when using threads

From
Nicolas Pitre <nico@cam.org>
Date
Dec 13, 2008, 19:27 UTC
Message-ID
<alpine.LFD.2.00.0812131425540.30035@xanadu.home>
In-Reply-To
<20081213133238.GA6718@sigill.intra.peff.net>
On Sat, 13 Dec 2008, Jeff King wrote:
Show 9 quoted lines
> On Thu, Dec 11, 2008 at 03:36:47PM -0500, Nicolas Pitre wrote:
> 
> > ... and display the actual number of threads used when locally 
> > repacking.  A remote server still won't tell you how many threads it 
> > uses during a fetch though.
> 
> Hrm. I have no idea how, but this patch reliably causes t5300 to fail on
> my FreeBSD test box ("next" is broken, bisection pointed to 43cc2b42).
> Sample verbose output is below.
Hmmm... Interesting.
Nicolas
Previous: Jeff KingNext: Nicolas Pitre
Message 5 of 11 in “autodetect number of CPUs by default when using threads”
  1. autodetect number of CPUs by default when using threadsNicolas Pitre, Dec 11, 2008
  2. Junio C HamanoDec 11, 2008
  3. Nicolas PitreDec 12, 2008
  4. Jeff KingDec 13, 2008
  5. Nicolas PitreDec 13, 2008
  6. pack-objects: don't use too many threads with few objectsNicolas Pitre, Dec 13, 2008
  7. Jeff KingDec 14, 2008
  8. Mike RalphsonDec 15, 2008
  9. Junio C HamanoDec 16, 2008
  10. Jeff KingDec 16, 2008
  11. Nicolas PitreDec 16, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.