On Fri, 2008-01-11 at 09:56 -0800, Rick Jones wrote: > >>The test command is: > >>#sudo taskset -c 7 ./netserver > >>#sudo taskset -c 0 ./netperf -t TCP_RR -l 60 -H 127.0.0.1 -i 50,3 -I 99,5 > >>-- -r 1,1 > > A couple of comments/questions on the command lines: Thanks for your kind comments.
> > *) netperf/netserver support CPU affinity within themselves with the > global -T option to netperf. Is the result with taskset much different? > The equivalent to the above would be to run netperf with: > > ./netperf -T 0,7 .. I checked the source codes and didn't find this option. I use netperf V2.3 (I found the number in the makefile). > . > > The one possibly salient difference between the two is that when done > within netperf, the initial process creation will take place wherever > the scheduler wants it. > > *) The -i option to set the confidence iteration count will silently cap > the max at 30. Indeed, you are right. -yanmin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
