From: Christian Loehle <CLoehle@hyperstone.com>
To: Richard Weinberger <richard@nod.at>,
Biju Das <biju.das.jz@bp.renesas.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
linux-renesas-soc <linux-renesas-soc@vger.kernel.org>,
wsa+renesas <wsa+renesas@sang-engineering.com>,
ulf hansson <ulf.hansson@linaro.org>
Subject: RE: Poor write performance to boot area using rcar-gen3-sdhi
Date: Tue, 18 Apr 2023 07:48:17 +0000 [thread overview]
Message-ID: <02ceda502af34bf0af53d52598a0b71f@hyperstone.com> (raw)
In-Reply-To: <971572458.117024.1681798584774.JavaMail.zimbra@nod.at>
Your eMMC likely treats the boot partitions differently than the user area, e.g. in regards to cache.
Is this reproducible for more 4k writes? What about larger writes?
The eMMC might not even have the mapping available after boot and first has to internally switch to it, in contrast to at u-boot stage?
Anyway this is probably more a question to your eMMC manufacturer and nothing the host is to be blamed, as you mentioned yourself, the time is spent at CMD25.
-----Original Message-----
From: Richard Weinberger <richard@nod.at>
Sent: Tuesday, April 18, 2023 8:16 AM
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>; linux-renesas-soc <linux-renesas-soc@vger.kernel.org>; wsa+renesas <wsa+renesas@sang-engineering.com>; ulf hansson <ulf.hansson@linaro.org>
Subject: Re: Poor write performance to boot area using rcar-gen3-sdhi
----- Ursprüngliche Mail -----
> Von: "Biju Das" <biju.das.jz@bp.renesas.com> Not sure, the file system
> used between /dev/mmcblk1boot1 and /dev/mmcblk1p13 is making
> difference at Linux?
>
> I have seen performance difference between FAT and ext4.
There is no filesystem, I'm writing directly using dd to the raw block device.
Thanks,
//richard
Hyperstone GmbH | Reichenaustr. 39a | 78467 Konstanz
Managing Director: Dr. Jan Peter Berns.
Commercial register of local courts: Freiburg HRB381782
next prev parent reply other threads:[~2023-04-18 8:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 20:08 Poor write performance to boot area using rcar-gen3-sdhi Richard Weinberger
2023-04-18 6:09 ` Biju Das
2023-04-18 6:16 ` Richard Weinberger
2023-04-18 7:48 ` Christian Loehle [this message]
2023-04-18 8:11 ` Richard Weinberger
2023-04-18 8:36 ` Christian Loehle
2023-04-18 11:58 ` Richard Weinberger
2023-04-20 15:18 ` Richard Weinberger
2023-04-21 16:23 ` Christian Loehle
2023-05-09 11:28 ` Richard Weinberger
2023-05-11 9:46 ` Christian Loehle
2023-05-11 10:35 ` Richard Weinberger
2023-04-18 8:12 ` Biju Das
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=02ceda502af34bf0af53d52598a0b71f@hyperstone.com \
--to=cloehle@hyperstone.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=richard@nod.at \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.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