[dm-devel] [PATCH v2 18/20] libmultipath: path latency: log threshold with p2
Guan Junxiong
guanjunxiong at huawei.com
Thu Feb 8 12:04:51 UTC 2018
Looks Good.
Reviewed-by: Guan Junxiong <guanjunxiong at huawei.com>
On 2018/1/14 5:19, Martin Wilck wrote:
> This is not a critical error. It just means that the path in
> question will have low priority (rightly so, if it has >100s latency).
> ---
> libmultipath/prioritizers/path_latency.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libmultipath/prioritizers/path_latency.c b/libmultipath/prioritizers/path_latency.c
> index b8c5bc7c50a4..ce5c95dd7075 100644
> --- a/libmultipath/prioritizers/path_latency.c
> +++ b/libmultipath/prioritizers/path_latency.c
> @@ -299,7 +299,7 @@ int getprio(struct path *pp, char *args, unsigned int timeout)
> (long long)pow(base_num, lg_avglatency));
>
> if (lg_avglatency > lg_maxavglatency) {
> - pp_pl_log(0,
> + pp_pl_log(2,
> "%s: average latency (%lld us) is outside the thresold (%lld us)",
> pp->dev, (long long)pow(base_num, lg_avglatency),
> (long long)MAX_AVG_LATENCY);
>
More information about the dm-devel
mailing list