public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: el_es <el.es.cr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Minimal jitter = good desktop.
Date: Sat, 6 Oct 2012 14:53:16 +0000 (UTC)	[thread overview]
Message-ID: <loom.20121006T164640-362@post.gmane.org> (raw)
In-Reply-To: op.wlrdzkqh6426ze@localhost.localdomain

Uwaysi Bin Kareem <uwaysi.bin.kareem <at> paradoxuncreated.com> writes:

[sorry for cutting out the context], but it's been topposted]

But the problem is, we cannot measure 'jitter' directly.
There is no reliable benchmark that produces results adherent
to what someones' definition of 'jitter' is.

At software level we only have a notion of latency, and that
leads to jitter as david said, but as the kernel is not real-time,
you cannot guarantee every opengl command/fb transfer will be finished
in time for next frame to be drawn.

Maybe if someone could get the information of % finished frames
(or % dropped frames) within one slice of userspace, that would 
be something to build on, but it's still a derivative and with 
unknown bias level.

Lukasz


  reply	other threads:[~2012-10-06 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06  0:49 Minimal jitter = good desktop Uwaysi Bin Kareem
2012-10-06  1:06 ` david
2012-10-06 13:19   ` Uwaysi Bin Kareem
2012-10-06 14:53     ` el_es [this message]
2012-10-06 18:02       ` Uwaysi Bin Kareem
2012-10-07  1:15         ` el_es
     [not found]           ` <op.wlsf0fuc6426ze@localhost.localdomain>
     [not found]             ` <CAEwFKRBk0X7vAh=Sw-imXeSLN8kBjdfWFXw0Vq2GGygS=0yPrA@mail.gmail.com>
     [not found]               ` <op.wltgb7mg6426ze@localhost.localdomain>
2012-10-07 20:28                 ` Uwaysi Bin Kareem

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=loom.20121006T164640-362@post.gmane.org \
    --to=el.es.cr@gmail.com \
    --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