GSoC: Add SMT/HT awareness to DragonFlyBSD scheduler
Matthew Dillon
dillon at apollo.backplane.com
Fri Jun 29 09:24:55 PDT 2012
: There shouldn't be much of any I/O waiting even with a hard drive
: for compilations. Apache (and other) builds are going to be limited
: by serialization within the Makefile and /bin/sh sequences which wind
: up doing a lot of fork/exec/wait's.
I should note that there will be one slight difference. Even
though disk I/O will minimally impact the build (particularly on the
second go-around), file operations can sometimes block for very
short periods of time in this situation, so the scheduler is going
to be exercised a lot more verses testing with simple cpu-bound
for(;;); loops.
-Matt
Matthew Dillon
<dillon at backplane.com>
More information about the Kernel
mailing list