From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Daejun Park <daejun7.park@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"tomas.winkler@intel.com" <tomas.winkler@intel.com>,
ALIM AKHTAR <alim.akhtar@samsung.com>,
"gregkh@google.com" <gregkh@google.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sang-yoon Oh <sangyoon.oh@samsung.com>,
Sung-Jun Park <sungjun07.park@samsung.com>,
yongmyung lee <ymhungry.lee@samsung.com>,
Jinyoung CHOI <j-young.choi@samsung.com>,
Adel Choi <adel.choi@samsung.com>,
BoRam Shin <boram.shin@samsung.com>,
SEUNGUK SHIN <seunguk.shin@samsung.com>
Subject: Re: [PATCH v13 0/3] scsi: ufs: Add Host Performance Booster Support
Date: Mon, 7 Dec 2020 19:35:03 +0100 [thread overview]
Message-ID: <X85116BXkgTtRDKV@kroah.com> (raw)
In-Reply-To: <20201207182603.GA2499@infradead.org>
On Mon, Dec 07, 2020 at 06:26:03PM +0000, Christoph Hellwig wrote:
> On Mon, Dec 07, 2020 at 07:23:12PM +0100, Greg KH wrote:
> > What "real workload" test can be run on this to help show if it is
> > useful or not? These vendors seem to think it helps for some reason,
> > otherwise they wouldn't have added it to their silicon :)
> >
> > Should they run fio? If so, any hints on a config that would be good to
> > show any performance increases?
>
> A real actual workload that matters. Then again that was Martins
> request to even justify it. I don't think the broken addressing that
> breaks a whole in the SCSI addressing has absolutely not business being
> supported in Linux ever. The vendors should have thought about the
> design before committing transistors to something that fundamentally
> does not make sense.
So "time to boot an android system with this enabled and disabled" would
be a valid workload, right? I'm guessing that's what the vendors here
actually care about, otherwise there is no real stress-test on a UFS
system that I know of.
thanks,
greg k-h
next prev parent reply other threads:[~2020-12-07 18:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201103044021epcms2p8f1556853fc23414442b9e958f20781ce@epcms2p8>
2020-11-03 4:40 ` [PATCH v13 0/3] scsi: ufs: Add Host Performance Booster Support Daejun Park
2020-11-03 4:46 ` [PATCH v13 1/3] scsi: ufs: Introduce HPB feature Daejun Park
2020-12-07 18:04 ` Greg KH
2020-12-15 1:24 ` Daejun Park
2020-11-03 4:47 ` [PATCH v13 2/3] scsi: ufs: L2P map management for HPB read Daejun Park
2020-11-03 4:47 ` [PATCH v13 3/3] scsi: ufs: Prepare HPB read for cached sub-region Daejun Park
2020-11-05 8:16 ` [PATCH v13 0/3] scsi: ufs: Add Host Performance Booster Support Can Guo
2020-12-07 17:56 ` Greg KH
2020-12-07 18:06 ` Christoph Hellwig
2020-12-07 18:23 ` Greg KH
2020-12-07 18:26 ` Christoph Hellwig
2020-12-07 18:35 ` Greg KH [this message]
2020-12-07 18:36 ` Greg KH
2020-12-07 18:54 ` James Bottomley
2020-12-07 19:08 ` Greg KH
2020-12-08 4:12 ` Daejun Park
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=X85116BXkgTtRDKV@kroah.com \
--to=greg@kroah.com \
--cc=adel.choi@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=boram.shin@samsung.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=daejun7.park@samsung.com \
--cc=gregkh@google.com \
--cc=hch@infradead.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=martin.petersen@oracle.com \
--cc=sangyoon.oh@samsung.com \
--cc=seunguk.shin@samsung.com \
--cc=stanley.chu@mediatek.com \
--cc=sungjun07.park@samsung.com \
--cc=tomas.winkler@intel.com \
--cc=ymhungry.lee@samsung.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