mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Avri Altman <Avri.Altman@wdc.com>
To: Lu Hongfei <luhongfei@vivo.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Bart Van Assche <bvanassche@acm.org>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Daniil Lunev <dlunev@chromium.org>,
	Jinyoung Choi <j-young.choi@samsung.com>,
	Bean Huo <beanhuo@micron.com>,
	Peter Wang <peter.wang@mediatek.com>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER" 
	<linux-scsi@vger.kernel.org>
Cc: "opensource.kernel@vivo.com" <opensource.kernel@vivo.com>
Subject: RE: [PATCH v4] scsi: ufs: wb: Add explicit flush_threshold sysfs attribute
Date: Fri, 9 Jun 2023 10:18:07 +0000	[thread overview]
Message-ID: <DM6PR04MB65755CFCA912182C5D5044BFFC51A@DM6PR04MB6575.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20230609091113.22531-1-luhongfei@vivo.com>

> 
> There are three flags that control Write Booster Feature:
> 
>     1. WB ON/OFF
>     2. WB Hibern Flush ON/OFF (implicitly)
>     3. WB Flush ON/OFF (explicit)
> 
> In the case of "Hibern Flush", one of the conditions for flush WB buffer is
> that avail_wb_buff < wb_flush_threshold.
> 
> As we know, different users have different requirements for power
> consumption and performance. Therefore, we need the ability to manually
> set wb_flush_threshold, so that users can easily and flexibly adjust
> the wb_flush_threshold value, thereby achieving a balance between power
> consumption and performance.
> 
> So the sysfs attribute that controls this is necessary.
> 
> The meaning of wb_flush_threshold is the percentage of WB's total size,
> such as 1 representing 10%, 2 representing 20%, and so on.
> 
> Signed-off-by: Lu Hongfei <luhongfei@vivo.com>
Reviewed-by: Avri Altman <avri.altman@wdc.com>

  reply	other threads:[~2023-06-09 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  9:11 Lu Hongfei
2023-06-09 10:18 ` Avri Altman [this message]
2023-06-12 18:21 ` Bart Van Assche

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR04MB65755CFCA912182C5D5044BFFC51A@DM6PR04MB6575.namprd04.prod.outlook.com \
    --to=avri.altman@wdc.com \
    --cc=alim.akhtar@samsung.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=dlunev@chromium.org \
    --cc=j-young.choi@samsung.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=luhongfei@vivo.com \
    --cc=martin.petersen@oracle.com \
    --cc=opensource.kernel@vivo.com \
    --cc=peter.wang@mediatek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®