I just tried that change and it didn't affect the results in
any significant way.
Thanks
--
Steve
On 2010-04-22 18:14, FUJITA Tomonori wrote:
On Thu, 08 Apr 2010 09:06:26 -0700
Steven Wertheimer<steven.wertheimer@xxxxxxxxxx> wrote:
As I said, I have not instrumented tgtd, but it seems pretty clear that
one tgtd process becomes CPU-bound and is unable to do enough
local I/O to saturate all of the disks. I'm happy to instrument and re-run
if that would help.
Can you get better numbers if you increase NR_WORKER_THREADS like
this?
diff --git a/usr/bs_thread.h b/usr/bs_thread.h
index 9dfbbd5..3640da2 100644
--- a/usr/bs_thread.h
+++ b/usr/bs_thread.h
@@ -1,4 +1,4 @@
-#define NR_WORKER_THREADS 4
+#define NR_WORKER_THREADS 16
typedef void (request_func_t) (struct scsi_cmd *);
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
