.
> In the meantime I'd argue for just getting rid of the online_cpu's
> check, because
> (a) I think it's actively misleading
> (b) the threaded grep probably doesn't hurt much even on a single
> CPU, and the _potential_ upside from IO could easily dwarf the cost.
> (c) do developers actually have single-core machines any more?
Linus
So as far as I understood your point at current moment would be better to leave online_cpus() check behind,
keep the default threads value (and do so for other threaded programs, in separate patches of course).
After that we may focus (in future) on developing smarter heuristics for parallelity-relationed params.
Also we should specify in documentation that number of your CPUs may not the optimal value and customer should find his own best values based on other circumstances.
Correct?
--
Victor--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html