For certain workloads, when/if the entire lun fits in page-cache you get better performance with only one single worker thread than multiple ones. This eliminates the context switching and bouncing between cores on a many-cores machine. So for certain workloads I want to use only one worker thread, and this parameter would allow me to do so without compiling up a separate version of tgtd. For these workloads, the single thread used to drive the eventsystem quickly becomes a bottleneck which is why I will also follow up with additional patches to make the portal address and the port configurable, to allow running multiple tgtd's on one system. One instance for each core, or pair of cores. regards ronnie sahlberg On Tue, Sep 22, 2009 at 3:35 PM, Tomasz Chmielewski <mangoo@xxxxxxxx> wrote: > ronnie sahlberg wrote: >> >> Hi, >> >> Please find attached a patch that removes the hardcoded number of >> threads and allows setting the number of worker threads from the >> commandline using the new arguments -t/--threads . >> The default value for number of threads, if -t/--threads are not >> specified, is 4, to match the behaviour of tgtd before this patch. > > In what usage scenarios can be this option useful? > > > -- > Tomasz Chmielewski > http://wpkg.org > -- 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
