From: Bart Van Assche <bvanassche@acm.org>
To: Can Guo <can.guo@oss.qualcomm.com>,
avri.altman@wdc.com, beanhuo@micron.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, Alim Akhtar <alim.akhtar@samsung.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Peter Wang <peter.wang@mediatek.com>,
Huan Tang <tanghuan@vivo.com>, Lu Hongfei <luhongfei@vivo.com>,
"Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
Yangtao Li <frank.li@vivo.com>,
Keoseong Park <keosung.park@samsung.com>,
Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>,
Liu Song <liu.song13@zte.com.cn>,
Ram Kumar Dwivedi <ram.dwivedi@oss.qualcomm.com>,
Daniel Lee <chullee@google.com>, Bean Huo <huobean@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/1] scsi: ufs: core: Add support to notify userspace of UniPro QoS events
Date: Thu, 5 Mar 2026 06:30:50 -0600 [thread overview]
Message-ID: <a079077d-ad7f-4dba-a72c-411740553529@acm.org> (raw)
In-Reply-To: <20260305110856.959211-2-can.guo@oss.qualcomm.com>
On 3/5/26 5:08 AM, Can Guo wrote:
> The UniPro stack manages to repair many potential Link problems without the
> need to notify the Application Layer. Repair mechanisms of the stack
> include L2 re-transmission and successful handling of PA_INIT.req.
> Nevertheless, any successful repair sequence requires Link bandwidth that
> is no longer vailable for the Application. Therefore, it may be useful for
> an Application to understand how often such repair attempts are made.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2026-03-05 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260305110856.959211-1-can.guo@oss.qualcomm.com>
2026-03-05 11:08 ` Can Guo
2026-03-05 12:30 ` Bart Van Assche [this message]
2026-03-06 7:11 ` Peter Wang (王信友)
2026-03-07 16:05 ` Martin K. Petersen
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=a079077d-ad7f-4dba-a72c-411740553529@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=can.guo@oss.qualcomm.com \
--cc=chullee@google.com \
--cc=frank.li@vivo.com \
--cc=huobean@gmail.com \
--cc=keosung.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liu.song13@zte.com.cn \
--cc=luhongfei@vivo.com \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=quic_nguyenb@quicinc.com \
--cc=ram.dwivedi@oss.qualcomm.com \
--cc=tanghuan@vivo.com \
--cc=zhongqiu.han@oss.qualcomm.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®