>During failover test, we found the iscsi over iser reconnected to the >iscs target after 100 seconds due to the default max timeout (8sec) and >retry number (15). The max timeout was adjustable with the module >parameter, max_timeout, of ib_cm.ko, but the retry number wasn't. Can we >add the retry number as module parameter of rdma_cm.ko? I added the >patch below based on the ofed version, OFED-1.2-20070626-0917.
Note that you can abort a connection operation by destroying the corresponding rdma_cm_id. Does iser try to re-establish a connection over the same path on failover? I'm wondering why it tried to connect over the failed path first. >+static int cma_max_cm_retries = CMA_MAX_CM_RETRIES; >+module_param_named(cma_max_cm_retries, cma_max_cm_retries, int, 0644); >+MODULE_PARM_DESC(cma_max_cm_retries, "the number of retry"); This must be a value between 0-15. I need to see if there's a better way to support users that want smaller connection timeouts. - Sean _______________________________________________ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg