All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 33977] X core font rendering is "laggy"
Date: Wed,  9 Feb 2011 03:54:42 -0800 (PST)	[thread overview]
Message-ID: <20110209115442.E32B7130051@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-33977-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=33977

--- Comment #11 from Michel Dänzer <michel@daenzer.net> 2011-02-09 03:54:42 PST ---
(In reply to comment #10)
> I was more worried about the xserver-exa side latency. It would be nice to have
> some kind of maximum latency. The driver can't do anything if the pixmap isn't
> anywhere in the driver.

Hmm, that's a good point. So if you've double-checked that the driver is
flushing properly in the BlockHandler, and there's still no timeout interval in
exaDamageReport_mixed which provides a better tradeoff between latency and
throughput, let's leave it at that for now.


However, then the question remains what is the cause of the '[...] not
displayed until I generate more output or update some other part of the screen'
in this report. That doesn't sound like something your EXA change would help
with.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2011-02-09 11:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07  3:31 [Bug 33977] New: X core font rendering is "laggy" bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-33977-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-02-07  3:31   ` [Bug 33977] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07  3:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07  4:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07  9:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found]     ` <20110207091543.AA74D13004F-4GnqB8vgsbnwRzGw0Gvu8Q/tdpCO6/zZ@public.gmane.org>
2011-02-07  9:31       ` Didier Spaier
2011-02-07 16:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 17:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 18:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09  9:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 11:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 11:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 11:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 11:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-02-09 20:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 20:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 20:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-10  6:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 16:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 17:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 17:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=20110209115442.E32B7130051@annarchy.freedesktop.org \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.