linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Dave Airlie <airlied@redhat.com>
Cc: "Christian König" <christian.koenig@amd.com>,
	"Takashi Iwai" <tiwai@suse.de>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: Performance regression in ast drm driver
Date: Thu, 8 Nov 2018 13:05:09 +0100	[thread overview]
Message-ID: <20181108130509.3b2d42ff@endymion> (raw)
In-Reply-To: <20181101162707.598c1718@endymion>

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

  reply	other threads:[~2018-11-08 12:05 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 [this message]
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

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=20181108130509.3b2d42ff@endymion \
    --to=jdelvare@suse.de \
    --cc=airlied@redhat.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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).