Received: by 10.213.65.68 with SMTP id h4csp2045977imn; Sun, 1 Apr 2018 23:10:04 -0700 (PDT) X-Google-Smtp-Source: AIpwx49sEGqV0YRnANv4aKAzNFZu1VtNt4MyxIF1NnTeqCACiqX1yNpeQPK89m3t20nonHsVwhZ3 X-Received: by 10.99.97.149 with SMTP id v143mr5457217pgb.319.1522649403956; Sun, 01 Apr 2018 23:10:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522649403; cv=none; d=google.com; s=arc-20160816; b=l677JlHhth5l+nzIPkqDPMpisQKFnXc0O7GjI9lrtKD1YNsGrDMHf/eqLEuVep8KE/ u46+2EyMCPXkHcljdMD9aqwZAGTtqfh2SIfIdHYvqfrmH15zUyyP9boNsKOhPZM8/awk V9YwxMPRDNzIHO+3sSipGE2E4fKklarL9FNpn4iPz02nE1UHTmSwKo3wtLRuPVZDbrlD xt0yUvfMTXt5SK4Muk4xdDd+Ohd9yH7XxPVVgi1esbPeHNe2N6cx7XEiG5MLTzgyL3Rg 4Hpqtj1eFyKrXXbZBiju8Rffv/ZfYRlKfjzUad2bw9oUIMOSPFB6nYR7aDsq4XrZ+xzw x1zQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:arc-authentication-results; bh=YQFOXXcSluFmUmt1KKyanOiuNvV5wSC7tGkcj51NfNg=; b=nrK1+vt9B2qqVK99sDjZJaINJdCn6st+5CW8d9EqEgmYoCDwSDI8j0bzXY5coAgWU1 FZQgqTuA+UNS19+4juBD4I4Jv9OTxNUf+4cH6LuKzDPPWB3xd9p+p2OguLzBgueW0Op3 ndGZ9LLuGUSNNjDjFd5RAkVDabvDbGo1y2BbULtN1t46RwFD+C94fLpv9KpYO0jpXjDi f57nZvJCEDFkpn03+VtnyJgk8gSUkMuCLsaE5iOYb50Yi7C0KFMvc7DwQy4MzJKRDJkc InbH02OUFL/0iVjce6ykuplnZjEOSADvRd7AccT1rHPLK+OdRFqe8R9E8C/pom4Br+NI KKvA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h1si10186408pfn.266.2018.04.01.23.09.50; Sun, 01 Apr 2018 23:10:03 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754169AbeDBGIQ (ORCPT + 99 others); Mon, 2 Apr 2018 02:08:16 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:6717 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751639AbeDBGIP (ORCPT ); Mon, 2 Apr 2018 02:08:15 -0400 Received: from DGGEMS408-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 271AD170927D8; Mon, 2 Apr 2018 14:08:01 +0800 (CST) Received: from [127.0.0.1] (10.177.96.203) by DGGEMS408-HUB.china.huawei.com (10.3.19.208) with Microsoft SMTP Server id 14.3.361.1; Mon, 2 Apr 2018 14:08:00 +0800 Subject: =?UTF-8?Q?Re:_=e7=ad=94=e5=a4=8d:_Re:_[PATCH_v2]_scsi:_Introduce_sd?= =?UTF-8?Q?ev=5fprintk=5fratelimited_to_throttlefrequent_printk?= To: Sergey Senozhatsky , References: <5AC1976F.1040801@huawei.com> <201804021314481872986@zte.com.cn> <20180402052920.GF3795@jagdpanzerIV> CC: , , , , , , , , , From: Jason Yan Message-ID: <5AC1C8BF.1030503@huawei.com> Date: Mon, 2 Apr 2018 14:07:59 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20180402052920.GF3795@jagdpanzerIV> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.96.203] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018/4/2 13:29, Sergey Senozhatsky wrote: > On (04/02/18 13:14), wen.yang99@zte.com.cn wrote: >> >> > It's true that this print for the same device is useless. But it's >> > useful for different devices. Is it possible to limit the print only >> > for the same device? >> >> In our scene, it's just for the same device (q->queuedata), Thanks. > > Yes, what Jason meant was that rate limit struct is shared by different call > sites - including scsi_request_fn() from different devices. > > If device1->scsi_request_fn()->sdev_printk_ratelimited() causes printk rate > limit, then messages from device2->scsi_request_fn()->sdev_printk_ratelimited() > may be lost entirely, unless you have enough of them. > > -ss > Yes, that's exactly what I mean. Thanks, Jason > . >