From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Fighting tearing
Date: Sun, 09 Sep 2012 19:00:00 +0100 [thread overview]
Message-ID: <453bf0$5lpncj@azsmga001.ch.intel.com> (raw)
In-Reply-To: <fd15fa3f1bf7a9c36c0013ac9633424b@bwidawsk.net>
[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]
On Sun, 09 Sep 2012 10:55:46 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> On 2012-09-09 08:48, Roberth Sjonøy wrote:
> > Hello
> >
> > I run Arch Linux, with it's latest x.org and kernel, and I have
> > compiled libdrm and the intel driver from git, and I update it today.
> >
> > Buit this is issue exists even with the releases.
> >
> > WIth UXA, rendering of the windows in my XFCE4-desktop goes just
> > fines, good performance, windows (exspecially GTK+) doesn't hang
> > after
> > if I drag them over the screen, but there is lot of small tearing.
> > And I want this to go away, I do not use any kind of composition, and
> > I am using XFCEs window manager.
> >
> > Here is my xorg.conf
> >
> >
> > Section "ServerFlags"
> > Option "AutoAddDevices" "Off"
> > EndSection
> >
> > Section "InputDevice"
> > Identifier "Keyboard0"
> > Driver "keyboard"
> > Option "XkbLayout" "no"
> > EndSection
> >
> > Section "Device"
> > Identifier "Card0"
> > Driver "intel"
> > Option "AccelMethod" "UXA"
> > Option "TearFree" "true"
> > Option "MigrationHeuristic" "greedy"
> > Option "TripleBuffer" "true"
> > EndSection
> >
> > With SNA, the performance of the applications is muc much worse. If I
> > just replace UXA with SNA.
> >
> > Thanks in advance for any help.
> >
> > Regards,
> >
> > Roberth Sjonøy0
>
> Unfortunately it's often the case that tearing is pretty much
> unavoidable without a compositor. AFAIK you'd just be getting lucky with
> SNA, as opposed to UXA.
Not so. He is explicitly asking for slow tear-free rendering with
Option "TearFree" "true". On my machines that takes about a 50%
performance hit which suggests pebkac which is reinforced by the lack
of information.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-09-09 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 15:48 Fighting tearing Roberth Sjonøy
2012-09-09 16:42 ` Paul Menzel
[not found] ` <CAFLBWR1jOM=87-GYWZVwdk70GBGGMrhWrvqkSU_7sQA2BrTB+g@mail.gmail.com>
2012-09-09 17:16 ` Fwd: " Roberth Sjonøy
[not found] ` <CAFLBWR0S8D-Y1O9gWXhySg-0VkVyxeXSi-nw7Ai8ZNoHEMpKmQ@mail.gmail.com>
2012-09-09 17:17 ` Roberth Sjonøy
2012-09-09 17:55 ` Ben Widawsky
2012-09-09 18:00 ` Chris Wilson [this message]
2012-09-09 20:02 ` Roberth Sjonøy
2012-09-10 0:07 ` Roberth Sjonøy
2012-09-10 14:09 ` Roberth Sjonøy
2012-09-11 21:21 ` Ben Widawsky
2012-09-10 16:17 ` Adam Jackson
2012-09-10 16:38 ` Roberth Sjonøy
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='453bf0$5lpncj@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.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