From: Christian Loehle <CLoehle@hyperstone.com>
To: Richard Weinberger <richard@nod.at>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
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: Thu, 11 May 2023 09:46:20 +0000 [thread overview]
Message-ID: <94f03374781b4e978a39699815b21803@hyperstone.com> (raw)
In-Reply-To: <615854031.8233438.1683631700226.JavaMail.zimbra@nod.at>
-----Original Message-----
From: Richard Weinberger <richard@nod.at>
Sent: Tuesday, May 9, 2023 1:28 PM
To: Christian Loehle <CLoehle@hyperstone.com>
Cc: Biju Das <biju.das.jz@bp.renesas.com>; 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
> So I went down the rabbit hole.
> After analyzing the operation traces from Linux and u-boot in more detail I had another chat with the vendor. It turned out their boot area *is* different, it operates on a much larger internal block size.
>
> While u-boot does basically all IO with one op code, Linux's writeback via page cache writes 4k wise which leads to catastrophic performance.
> Using O_DIRECT mitigates the issue, though.
Interesting, without having tried it out I would expect the 4k writebacks to be merged to a bigger IO, too? Given that they are filled sequentially, which is the case.
But good that you got it working.
If I find the time I will play with it a bit.
>
> Thanks everyone for your valuable input!
> //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-05-11 9:46 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
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 [this message]
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=94f03374781b4e978a39699815b21803@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