Hi Or! Or Gerlitz schrieb:
Yes, you can patch the srp initiator code to disable fmr pool caching, with this patch, it also adds a print to see that fmrs are actually used, as under some page list patterns SRP may use "indirect mapping" which is not based on fmr. After seeing that the print does happen, you may want to remove it.
[53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384075] srp fmr mapping done, va 0 [53654.384718] srp fmr mapping done, va 0 [53654.384725] srp fmr mapping done, va 0 [53654.384729] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.392083] srp fmr mapping done, va 0 [53654.396084] srp fmr mapping done, va 0 [53654.396084] srp fmr mapping done, va 0 [53654.396084] srp fmr mapping done, va 0 [53654.396084] srp fmr mapping done, va 0 [53654.396084] srp fmr mapping done, va 0 [53654.396084] srp fmr mapping done, va 0 [53654.396084] srp fmr mapping done, va 0 [53654.396084] srp fmr mapping done, va 0 [53656.835768] iser: iscsi_iser_ep_disconnect:ib conn ffff8104205ac6c0 state 4 [53656.835915] iser: iser_free_ib_conn_res:freeing conn ffff8104205ac6c0 cma_id ffff810415889200 fmr pool ffff8104200fde40 qp ffff810402513c00 [53656.839736] iser: iser_device_try_release:device ffff8104200eb140 refcount 0 [53656.839736] iser: iser_connect:connecting to: 10.1.3.32, port 0xbc0c [53656.844706] iser: iser_cma_handler:event 0 conn ffff8104205ac6c0 id ffff81042485c400 [53656.845280] iser: iser_cma_handler:event 2 conn ffff8104205ac6c0 id ffff81042485c400 [53657.115731] iser: iser_create_ib_conn_res:setting conn ffff8104205ac6c0 cma_id ffff81042485c400: fmr_pool ffff8104164a6f40 qp ffff810402513a00 [53657.115731] iser: iser_cma_handler:event 8 conn ffff8104205ac6c0 id ffff81042485c400 [53657.115731] iser: iser_cma_handler:event: 8, error: 8 [53657.369163] iser: iscsi_iser_ep_poll:ib conn ffff8104205ac6c0 rc = -1 All lmdd tests run without a single problem. So SRP/SCST seems not to be affected by this patch. Ony other ideas? Cheers Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== -- 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
