From: YC Chen <yc_chen@aspeedtech.com>
To: Jean Delvare <jdelvare@suse.de>, Dave Airlie <airlied@redhat.com>
Cc: "Christian König" <christian.koenig@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"YC Chen" <yc_chen@aspeedtech.com>
Subject: RE: Performance regression in ast drm driver
Date: Tue, 13 Nov 2018 08:19:46 +0000 [thread overview]
Message-ID: <985f3dff65744a1899cb012cbb3d4156@TWMBX01.aspeed.com> (raw)
In-Reply-To: <20181108130509.3b2d42ff@endymion>
Sir,
We found the performance will be bad on desktop environment with OpenSUSE15 UEFI installation if remove "arch_io_reserve_memtype_wc".
Regards,
Y.C. Chen
-----Original Message-----
From: dri-devel [mailto:dri-devel-bounces@lists.freedesktop.org] On Behalf Of Jean Delvare
Sent: Thursday, November 08, 2018 8:05 PM
To: Dave Airlie <airlied@redhat.com>
Cc: Christian König <christian.koenig@amd.com>; dri-devel@lists.freedesktop.org; linux-kernel@vger.kernel.org
Subject: Re: Performance regression in ast drm driver
On Thu, 1 Nov 2018 16:27:07 +0100, Jean Delvare wrote:
> Hi David,
>
> The following commit:
>
> commit 7cf321d118a825c1541b43ca45294126fd474efa
> Author: Dave Airlie
> Date: Mon Oct 24 15:37:48 2016 +1000
>
> drm/drivers: add support for using the arch wc mapping API.
>
> is causing a huge performance regression for the ast drm driver. In a
> text console, if I call "cat" on a large text file, it takes almost
> twice as much time to be displayed and scrolled completely.
>
> Can you please check that the ast driver portion of that commit is
> both correct and complete?
And in the meantime, what bad will happen if we just revert the ast portion of that commit?
Thanks,
--
Jean Delvare
SUSE L3 Support
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-11-13 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 15:27 Performance regression in ast drm driver Jean Delvare
2018-11-08 12:05 ` Jean Delvare
2018-11-09 0:04 ` David Airlie
2018-11-10 8:39 ` Jean Delvare
2018-11-12 14:36 ` Jean Delvare
2018-11-12 14:45 ` Takashi Iwai
2018-11-12 16:41 ` Jean Delvare
2018-11-13 9:23 ` Thomas Zimmermann
2018-11-13 12:08 ` Jean Delvare
2018-11-13 12:16 ` Thomas Zimmermann
2018-11-12 19:36 ` Thomas Zimmermann
2018-11-13 8:19 ` YC Chen [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=985f3dff65744a1899cb012cbb3d4156@TWMBX01.aspeed.com \
--to=yc_chen@aspeedtech.com \
--cc=airlied@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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).