All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: [Regression 5.5-rc1] Extremely low GPU performance on NVIDIA Tegra20/30
Date: Fri, 13 Dec 2019 00:25:33 +0300	[thread overview]
Message-ID: <a2c9eb65-c600-bf49-2c32-bddf7b44f784@gmail.com> (raw)

Hello Thierry,

Commit [1] introduced a severe GPU performance regression on Tegra20 and
Tegra30 using.

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.5-rc1&id=fa6661b7aa0b52073681b0d26742650c8cbd30f3

Interestingly the performance is okay on Tegra30 if
CONFIG_TEGRA_HOST1X_FIREWALL=n, but that doesn't make difference for
Tegra20.

I was telling you about this problem on the #tegra IRC sometime ago and
you asked to report it in a trackable form, so finally here it is.

You could reproduce the problem by running [2] like this
`grate/texture-filter -f -s` which should produce over 100 FPS for 720p
display resolution and currently it's ~11 FPS.

[2]
https://github.com/grate-driver/grate/blob/master/tests/grate/texture-filter.c

Previously I was seeing some memory errors coming from Host1x DMA, but
don't see any errors at all right now.

I don't see anything done horribly wrong in the offending commit.

Unfortunately I couldn't dedicate enough time to sit down and debug the
problem thoroughly yet. Please let me know if you'll find a solution,
I'll be happy to test it. Thanks in advance!

WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: [Regression 5.5-rc1] Extremely low GPU performance on NVIDIA Tegra20/30
Date: Fri, 13 Dec 2019 00:25:33 +0300	[thread overview]
Message-ID: <a2c9eb65-c600-bf49-2c32-bddf7b44f784@gmail.com> (raw)

Hello Thierry,

Commit [1] introduced a severe GPU performance regression on Tegra20 and
Tegra30 using.

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.5-rc1&id=fa6661b7aa0b52073681b0d26742650c8cbd30f3

Interestingly the performance is okay on Tegra30 if
CONFIG_TEGRA_HOST1X_FIREWALL=n, but that doesn't make difference for
Tegra20.

I was telling you about this problem on the #tegra IRC sometime ago and
you asked to report it in a trackable form, so finally here it is.

You could reproduce the problem by running [2] like this
`grate/texture-filter -f -s` which should produce over 100 FPS for 720p
display resolution and currently it's ~11 FPS.

[2]
https://github.com/grate-driver/grate/blob/master/tests/grate/texture-filter.c

Previously I was seeing some memory errors coming from Host1x DMA, but
don't see any errors at all right now.

I don't see anything done horribly wrong in the offending commit.

Unfortunately I couldn't dedicate enough time to sit down and debug the
problem thoroughly yet. Please let me know if you'll find a solution,
I'll be happy to test it. Thanks in advance!
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-12-12 21:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 21:25 Dmitry Osipenko [this message]
2019-12-12 21:25 ` [Regression 5.5-rc1] Extremely low GPU performance on NVIDIA Tegra20/30 Dmitry Osipenko
2019-12-13 15:10 ` Thierry Reding
2019-12-13 15:35   ` Dmitry Osipenko
     [not found]     ` <d03876b8-b0d1-850b-7ae8-a61302e23843-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-01-20  2:53       ` Dmitry Osipenko
2020-01-20  2:53         ` Dmitry Osipenko
     [not found]         ` <2f5c6fda-adf9-c6c3-7601-fa912813ce1f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-01-28 15:43           ` Dmitry Osipenko
2020-01-28 15:43             ` Dmitry Osipenko
2020-01-29 12:39           ` Thierry Reding
2020-01-29 12:39             ` Thierry Reding
2020-01-30  4:36             ` Dmitry Osipenko
2020-01-30  4:36               ` Dmitry Osipenko
     [not found]               ` <d69df90f-37c9-0242-708a-689a8789a30b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-01-30 12:08                 ` Thierry Reding
2020-01-30 12:08                   ` Thierry Reding
2020-02-02 21:00                   ` Dmitry Osipenko
2020-02-02 21:00                     ` Dmitry Osipenko
     [not found]                     ` <7b710148-15db-f2d8-4221-62b032542426-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-02-03 12:56                       ` Thierry Reding
2020-02-03 12:56                         ` Thierry Reding

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=a2c9eb65-c600-bf49-2c32-bddf7b44f784@gmail.com \
    --to=digetx@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-tegra@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.