fio seems to assign the same cpus_allowed/cpumask value to all threads. I think this allows the OS to move the threads around those CPUs. In comparison, iometer assigns its worker threads to specific CPUs within the cpumask in round-robin manner. Would that be worth adding to fio, perhaps with an option like cpus_allowed_policy=roundrobin? --- Rob Elliott HP Server Storage -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
