From: "Christian Löhle" <CLoehle@hyperstone.com>
To: "Christian Löhle" <CLoehle@hyperstone.com>,
"Wenchao Chen" <wenchao.chen666@gmail.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"orsonzhai@gmail.com" <orsonzhai@gmail.com>,
"baolin.wang@linux.alibaba.com" <baolin.wang@linux.alibaba.com>,
"zhang.lyra@gmail.com" <zhang.lyra@gmail.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"kch@nvidia.com" <kch@nvidia.com>
Cc: "vincent.whitchurch@axis.com" <vincent.whitchurch@axis.com>,
"bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"s.shtylyov@omp.ru" <s.shtylyov@omp.ru>,
"michael@allwinnertech.com" <michael@allwinnertech.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"megoo.tang@gmail.com" <megoo.tang@gmail.com>,
"lzx.stg@gmail.com" <lzx.stg@gmail.com>
Subject: RE: [PATCH V2 0/2] mmc: block: Support Host to control FUA
Date: Fri, 21 Oct 2022 16:32:39 +0000 [thread overview]
Message-ID: <0a9cf24cb65d49838c95455bb54ebf10@hyperstone.com> (raw)
In-Reply-To: <e7858446b9604b59b8270f181a1410ef@hyperstone.com>
>
> Unless there is something special / wrong with sdhci-sprd (unlikely? Its just a flag) or your eMMC (maybe more likely?) then Id expect this or similar performance degradation for any host controller and eMMC.
> I can redo some measurement if you provide your workload.
> But I'd say if you don’t want to pay the price of reliable write then make sure to not issue them, by not issuing FUA?
> Maybe I'm misunderstanding, but why would the host controller driver control FUA?
>
Maybe one more point on that: Compare performance with fua disabled but cache off, should be comparable unless there is an actual reliable write problem.
If reliable write is performing horribly on that eMMC maybe a quirk could be thought of.
Anyway your 13MB/s random with fua, if a reliable write is basically always active for a given cache size,
doesn't sound totally unreasonable (over 3000 IOPS, assuming 4k writes).
Hyperstone GmbH | Reichenaustr. 39a | 78467 Konstanz
Managing Director: Dr. Jan Peter Berns.
Commercial register of local courts: Freiburg HRB381782
prev parent reply other threads:[~2022-10-21 16:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 7:30 [PATCH V2 0/2] mmc: block: Support Host to control FUA Wenchao Chen
2022-10-21 7:30 ` [PATCH V2 1/2] " Wenchao Chen
2022-10-21 7:53 ` Avri Altman
2022-10-21 8:47 ` Wenchao Chen
2022-10-21 9:37 ` Avri Altman
2022-10-21 7:30 ` [PATCH V2 2/2] mmc: sdhci-sprd: enable fua_disable for SPRDSDHCI Wenchao Chen
2022-10-21 9:42 ` [PATCH V2 0/2] mmc: block: Support Host to control FUA Avri Altman
2022-10-21 15:50 ` Adrian Hunter
2022-11-11 7:58 ` Wenchao Chen
2022-11-11 11:34 ` Ulf Hansson
2022-11-11 12:04 ` Ulf Hansson
2023-02-09 14:50 ` Ulf Hansson
2023-02-13 8:21 ` Wenchao Chen
2023-02-15 15:13 ` Ulf Hansson
2022-11-18 10:11 ` Adrian Hunter
2022-11-18 10:54 ` Wenchao Chen
2022-11-18 11:26 ` Adrian Hunter
2022-10-21 16:10 ` Christian Löhle
2022-10-21 16:32 ` Christian Löhle [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=0a9cf24cb65d49838c95455bb54ebf10@hyperstone.com \
--to=cloehle@hyperstone.com \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=axboe@kernel.dk \
--cc=baolin.wang@linux.alibaba.com \
--cc=bigeasy@linutronix.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lzx.stg@gmail.com \
--cc=megoo.tang@gmail.com \
--cc=michael@allwinnertech.com \
--cc=orsonzhai@gmail.com \
--cc=s.shtylyov@omp.ru \
--cc=ulf.hansson@linaro.org \
--cc=vincent.whitchurch@axis.com \
--cc=wenchao.chen666@gmail.com \
--cc=zhang.lyra@gmail.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;
as well as URLs for NNTP newsgroup(s).