From: Dmitry Osipenko <digetx@gmail.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Matt Merhar <mattmerhar@protonmail.com>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Chauvet <kwizart@gmail.com>,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v15 1/2] drm/tegra: dc: Support memory bandwidth management
Date: Wed, 17 Mar 2021 01:56:38 +0300 [thread overview]
Message-ID: <49a69c69-44e7-741f-b86b-ef4fe83c76b1@gmail.com> (raw)
In-Reply-To: <1158bbca-8880-918d-7564-e2e30552e6b3@gmail.com>
15.03.2021 21:39, Dmitry Osipenko пишет:
>>> + /*
>>> + * Horizontal downscale needs a lower memory latency, which roughly
>>> + * depends on the scaled width. Trying to tune latency of a memory
>>> + * client alone will likely result in a strong negative impact on
>>> + * other memory clients, hence we will request a higher bandwidth
>>> + * since latency depends on bandwidth. This allows to prevent memory
>>> + * FIFO underflows for a large plane downscales, meanwhile allowing
>>> + * display to share bandwidth fairly with other memory clients.
>>> + */
>>> + if (src_w > dst_w)
>>> + mul = (src_w - dst_w) * bpp / 2048 + 1;
>>> + else
>>> + mul = 1;
>> [...]
>>
>> One point is unexplained yet: why is the multiplier proportional to a
>> *difference* between src and dst widths? Also, I would expect max (worst
>> case) is pixclock * read_size when src_w/dst_w >= read_size.
> IIRC, the difference gives a more adequate/practical result than the
> proportion. Although, downstream driver uses proportion. I'll try to
> revisit this for the next version of the patch.
I tried to re-test everything and can't reproduce problems that existed
previously. We didn't have a finished memory drivers back then and I
think that Tegra30 latency tuning support and various Tegra20 changes
fixed those problems. I'll remove this hunk in the next version.
next prev parent reply other threads:[~2021-03-16 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:22 [PATCH v15 0/2] Add memory bandwidth management to NVIDIA Tegra DRM driver Dmitry Osipenko
2021-03-11 17:22 ` [PATCH v15 1/2] drm/tegra: dc: Support memory bandwidth management Dmitry Osipenko
2021-03-14 22:31 ` Michał Mirosław
2021-03-15 18:39 ` Dmitry Osipenko
2021-03-16 22:56 ` Dmitry Osipenko [this message]
2021-03-11 17:22 ` [PATCH v15 2/2] drm/tegra: dc: Extend debug stats with total number of events Dmitry Osipenko
2021-03-14 22:11 ` Michał Mirosław
2021-03-17 17:44 ` Dmitry Osipenko
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=49a69c69-44e7-741f-b86b-ef4fe83c76b1@gmail.com \
--to=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=kwizart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=pgwipeout@gmail.com \
--cc=thierry.reding@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
Powered by JetHome