multipath.conf : no_path_retry setting seem to translate to queue_if_no_path

This is regarding no_path_retry setting in multipath.conf. After going through the multipath tools src code it seems like this setting is represented as "queue_if_no_path" internally. The DM driver code also deals with "queue_if_no_path" only. Due to this reason the setting of "no_path_retry" to a numerical value is not working if both the path fails i.e in case of no path and the IO hangs. Also from the dm driver code it seems like to avoid the IO hang we need to set queue_if_no_path_timeout_secs. Please confirm the behaviour.