Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp1716077rwl; Thu, 5 Jan 2023 18:43:38 -0800 (PST) X-Google-Smtp-Source: AMrXdXsGP5ZmomrbNvVeruyZB0UVmKxJbALL9fQXA5BrT/WfNQGVIqcvLo1VkZJb6YpGp+hzt7zX X-Received: by 2002:a17:902:ed89:b0:192:816c:8c31 with SMTP id e9-20020a170902ed8900b00192816c8c31mr34906835plj.35.1672973018625; Thu, 05 Jan 2023 18:43:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672973018; cv=none; d=google.com; s=arc-20160816; b=ygsSgboWdZLilnigZyWrrJiUS1fl3iz2cfSz9jBXh7YpieRtjXynjH8x6ovRh9uVJ9 N/jub3q8TcE7783BgAujnHrGtUbSEQRmYyiVgsaErwa/wA+UPUIGXKKmOJVrj2BfxuXm W7iul2rCv646K8LQqwcsjklUaOrNS/XhqjkFBpnwcpgkO9aLUVZRzk+LbmjvBVfVI9ql PiQM2dABOQwssF5/bhUdSGLxybLV3Y1OD2G+n0F4bK7wT+4Hgm9BwS7wn2QoARWfJUhM cxxi8RjliIwMLUPbmJKJz+Bmu7cpHcf4TVGmgxy2eJBBkx/bfyQn16CAQpo9Yr5Z/wrN s58A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:dlp-filter:cms-type :content-transfer-encoding:date:message-id:in-reply-to:cc:to:from :sender:reply-to:subject:mime-version:dkim-signature:dkim-filter; bh=zYAVVwKbYWstk25NjpAYrxBF81yAcrHna5VCyCM4pz8=; b=kF/97INrN8daLGgHW56Pw/ph9+p+LdI2D3JWfO5nY48dlRT4jvxe5bK7bdnlBs/q+K H9k70D/PLNSGjn3ep82Evjs/IkxcR2BCN2lhYn5WgOhgydPJFC/bg5Cd9jVmbGQOP9x9 4hMpyadwbBmrO80J5JmjlkyF61I5JVCOeJLMJplM/sROk5x1MOX9DBHULex1SzQernNG ZPD9nytpStyMi6wD0EWYmSYHUW462HGUxmB6rxEHPhqn6VwWIhKpei2HZHsX29IDZltT e8mVfAOmQs/lePP2r9sknRL8istNJQm9gox+wCVO3C4ilyl9E4CJaooDULeZuAtyQxw3 w7Gg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@samsung.com header.s=mail20170921 header.b=mtMuKQAP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=samsung.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w21-20020a170902d71500b0018905bd4a58si9095156ply.169.2023.01.05.18.43.31; Thu, 05 Jan 2023 18:43:38 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@samsung.com header.s=mail20170921 header.b=mtMuKQAP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=samsung.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229532AbjAFCZI (ORCPT + 55 others); Thu, 5 Jan 2023 21:25:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42778 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229530AbjAFCZE (ORCPT ); Thu, 5 Jan 2023 21:25:04 -0500 Received: from mailout4.samsung.com (mailout4.samsung.com [203.254.224.34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 135F563F5A for ; Thu, 5 Jan 2023 18:25:01 -0800 (PST) Received: from epcas2p3.samsung.com (unknown [182.195.41.55]) by mailout4.samsung.com (KnoxPortal) with ESMTP id 20230106022457epoutp04fcbaf4876eed161e7b6ef0ba78df5838~3lxO3HQTr2542625426epoutp04J for ; Fri, 6 Jan 2023 02:24:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout4.samsung.com 20230106022457epoutp04fcbaf4876eed161e7b6ef0ba78df5838~3lxO3HQTr2542625426epoutp04J DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1672971897; bh=zYAVVwKbYWstk25NjpAYrxBF81yAcrHna5VCyCM4pz8=; h=Subject:Reply-To:From:To:CC:In-Reply-To:Date:References:From; b=mtMuKQAPQ5gb4u0njOYlSAGUXfO60S83nMptdarFtNEE07qbA+XQpbza2kUocTw2i f5OvZIsYVsK10mFrw0NAMK0d5CYOSUBx7ex60BKAQ2dqd5ezUq/uUK7f5XN8tuSaye BoSddzSg6iwwWUpjCWBXTPNoE/Xw3E2LROsf3yaY= Received: from epsnrtp3.localdomain (unknown [182.195.42.164]) by epcas2p1.samsung.com (KnoxPortal) with ESMTP id 20230106022457epcas2p1e8b266521fd8f3ab2e6b8cec6ec29135~3lxOdNyH42057020570epcas2p1i; Fri, 6 Jan 2023 02:24:57 +0000 (GMT) Received: from epsmges2p3.samsung.com (unknown [182.195.36.102]) by epsnrtp3.localdomain (Postfix) with ESMTP id 4Np6cS3djLz4x9Q0; Fri, 6 Jan 2023 02:24:56 +0000 (GMT) X-AuditID: b6c32a47-619ff7000000f187-f5-63b786783a81 Received: from epcas2p3.samsung.com ( [182.195.41.55]) by epsmges2p3.samsung.com (Symantec Messaging Gateway) with SMTP id 51.0F.61831.87687B36; Fri, 6 Jan 2023 11:24:56 +0900 (KST) Mime-Version: 1.0 Subject: RE:(2) [PATCH] scsi: ufs: core: fix devfreq deadlocks Reply-To: j-young.choi@samsung.com Sender: Jinyoung CHOI From: Jinyoung CHOI To: Avri Altman , Bart Van Assche , Asutosh Das CC: Johan Hovold , "James E.J. Bottomley" , "Martin K. Petersen" , ALIM AKHTAR , "linux-scsi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , Can Guo X-Priority: 3 X-Content-Kind-Code: NORMAL In-Reply-To: X-CPGS-Detection: blocking_info_exchange X-Drm-Type: N,general X-Msg-Generator: Mail X-Msg-Type: PERSONAL X-Reply-Demand: N Message-ID: <20230106022456epcms2p784b3cf9115f6b170bdef0732258381ba@epcms2p7> Date: Fri, 06 Jan 2023 11:24:56 +0900 X-CMS-MailID: 20230106022456epcms2p784b3cf9115f6b170bdef0732258381ba Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Sendblock-Type: AUTO_CONFIDENTIAL X-CPGSPASS: Y X-CPGSPASS: Y CMS-TYPE: 102P X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMJsWRmVeSWpSXmKPExsWy7bCmuW5F2/Zkg0+XxSwezNvGZvHy51U2 i2kffjJbvDykabHoxjYmixWVFpd3zWGz6L6+g81i+fF/TBYLO+ayWEy6toHNYsHGR4wOPB6X r3h7bFrVyeYxYdEBRo+PT2+xeEzcU+fRt2UVo8fnTXIe7Qe6mQI4orJtMlITU1KLFFLzkvNT MvPSbZW8g+Od403NDAx1DS0tzJUU8hJzU22VXHwCdN0yc4AuVVIoS8wpBQoFJBYXK+nb2RTl l5akKmTkF5fYKqUWpOQUmBfoFSfmFpfmpevlpZZYGRoYGJkCFSZkZ9x9/pCpYBVnxew5p5ka GFexdzFyckgImEj0Tl3FCmILCexglDjaYdXFyMHBKyAo8XeHMEhYWMBOYs+x68wQJUoS59bM YgQpERYwkLjVaw4SZhPQk/i5ZAYbSFhEoEzizeWYLkYuDmaBTmaJB3sXQ23ilZjR/pQFwpaW 2L58KyOIzSkQK7H60wxmiLiGxI9lvVC2qMTN1W/ZYez3x+YzQtgiEq33zkLVCEo8+LkbKi4p cejQV7AbJATyJTYcCIQI10i8XX4AqkRf4lrHRhaIB30lvvV5gIRZBFQl/k2/CDXRReL8vD6w rcwC8hLb385hBilnFtCUWL9LH2K4ssSRWywwPzVs/M2OzmYW4JPoOPwXLr5j3hMmiFY1iUVN RhMYlWchwngWklWzEFYtYGRexSiWWlCcm55abFRgDI/V5PzcTYzg1KrlvoNxxtsPeocYmTgY DzFKcDArifCW9W9LFuJNSaysSi3Kjy8qzUktPsRoCvTkRGYp0eR8YHLPK4k3NLE0MDEzMzQ3 MjUwVxLnDdo6P1lIID2xJDU7NbUgtQimj4mDU6qBiel2a1D0/xDdE5+WTnwUvEqAXf8Yi/ak SFUG13+m8kvNW1jXPzvxsaFW7siX34cOc+463PP6Mff2YxvcIwLXdjWHfvv2zJTpXqZKUKNc laTdVOcU6z0PFujW8P230z1ed7XlSXJF0eyFS24Z9oflihhPYb3mzbHVddLRyyt+b9hhezQ8 wSJrc65WX4wC3+w3X5LlnKXWPWS5tXH9uUNStcGLtwsucTfeWlVzRPmDVuJ6RVuW1dUn+ESq zh87NmlN1pH7LFZzp9qeyZade5OvpdS81GkuY8nVlR5HLYI1+id6+ky8saLWun/zqrXl6d+j IkS2HLj8WO6nlPTTecubku8oxLw223/x+qRH1qy1k5RYijMSDbWYi4oTAbW/Hvo2BAAA DLP-Filter: Pass X-CFilter-Loop: Reflected X-CMS-RootMailID: 20230105072134epcas2p47a72da1ee48e341295575770d3eb573c References: <20221222102121.18682-1-johan+linaro@kernel.org> <85e91255-1e6f-f428-5376-08416d2107a2@acm.org> <20230104141045.GB8114@asutoshd-linux1.qualcomm.com> <3db8c140-2e4e-0d75-4d81-b2c1f22f68d1@acm.org> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> On 1/4/23 06:10, Asutosh Das wrote: >> > Load based toggling of WB seemed fine to me then. >> > I haven't thought about another method to toggle WriteBooster yet. >> > Let me see if I can come up with something. >> > IMT if you have a mechanism in mind, please let me know. >> >> Hi Asutosh, >> >> Which UFS devices need this mechanism? All UFS devices I'm familiar with can >> achieve wire speed for large write requests without enabling the WriteBooster. >This feature assures SLC-performance for writes to the WriteBooster buffer. >So enabling it is advantageous as far as write performance. I agree with you. Also, it can be used in various ways. >As for the toggling functionality, compared to e.g. enabling it on init and leave it on, >some flash vendors require it because of device health considerations. >This is not the case for us, so let others to comment. In our case, it does not matter whether to toggle or not. To make the code simple, it seems to be a good way to enable it on init and leave it on. Considering device health, WB can be disabled through lifetime check. Thanks, Jinyoung. > >Thanks, >Avri >> >> Thanks, >> >> Bart.