[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c6679d1-9492-6cfe-00ef-8f2308e67643@criteo.com>
Date: Fri, 1 Mar 2019 14:59:54 +0000
From: Erwan Velu <e.velu@...teo.com>
To: "Elliott, Robert (Persistent Memory)" <elliott@....com>,
Erwan Velu <erwanaliasr1@...il.com>
CC: Don Brace <don.brace@...rosemi.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
"open list:MICROSEMI SMART ARRAY SMARTPQI DRIVER (smartpqi)"
<esc.storagedev@...rosemi.com>,
"open list:MICROSEMI SMART ARRAY SMARTPQI DRIVER (smartpqi)"
<linux-scsi@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] scsi: smartpqi_init: Reporting 'logical unit failure'
[...]
> Be careful printing errors per-IO; you could get thousands of them if things go bad.
> The block layer print_req_error() uses printk_ratelimited(KERN_ERR) for that reason,
> and the SCSI layer scsi_io_completion_action() maintains a ratelimit on its own.
>
> The dev_err_ratelimited() macro might be a good fit here.
Thanks for the tip. I updated the patch and send a V2 for that.
I adjusted also to commit message to make it more explicit.
Thanks for the review.
Erwan,
Powered by blists - more mailing lists