From: Bart Van Assche <bvanassche@acm.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ufs: switch WriteBooster missing free space message as warn_once
Date: Mon, 6 Jul 2026 07:36:18 -0700 [thread overview]
Message-ID: <8dca295e-9c39-4707-bdd6-e4aeadbf780c@acm.org> (raw)
In-Reply-To: <20260618-topic-ufs-wb-empty-warn-v1-1-ec744a153e0e@linaro.org>
On 6/18/26 12:52 AM, Neil Armstrong wrote:
> Once the UFS WriteBooster fails to allocate memory, the situation
> will stay until fstrim or equivalent is ran.
>
> Mark is as a warning since it impacts the performance but only
> print it once for the lifetime of the kernel since it's not fatal.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
prev parent reply other threads:[~2026-07-06 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 7:52 [PATCH] ufs: switch WriteBooster missing free space message as warn_once Neil Armstrong
2026-07-06 14:36 ` Bart Van Assche [this message]
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=8dca295e-9c39-4707-bdd6-e4aeadbf780c@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=neil.armstrong@linaro.org \
/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