From: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
To: linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.6.2-rt4
Date: Sat, 27 Oct 2012 11:50:37 +0200 [thread overview]
Message-ID: <op.wmt0antg6426ze@millennium.getinternet.no> (raw)
In-Reply-To: <op.wms2phwb6426ze@millennium.getinternet.no>
I did some small edits, but not really any difference to how the kernel
works. Such as a 90hz timer. Which seemed to work the best here, for
lowest jitter in OpenGL. I have actually had a lot of fun with the kernel,
and games are indeed much more immersive with low-jitter. It just creates
a higher expectation to quality, and for some games also make some
paradigms a bit outdated. Such as some horrorscenes in doom 3. Doom 3
plays extremely well here now though. Also improving the action on the
fastest bus (PCIe), seem to generally improve the whole system.
Videojitter is lower, although ofcourse it needs to be completely fixed
with sync and refresh rate changes. System is more responsive. So I
believe that reducing jitter, seems central to a good computing experience.
Will be fun to try rt patch also, although current mainline is very close
to doing 0.2ms latency, there is just a few clicks at 0.3 (without
realtime threads) here. Meaning that os-jitter on average is lower than
0.2ms. Having used an amiga500, and knowing how that feels. 0.3ms feels
close, but maybe just a bit lower. So 0.2ms. And that is the kind of
computer I want.
I am also building a machine particulary for low-jitter.
http://paradoxuncreated.com/Blog/wordpress/?p=4176
So if we can`t get RT running on this one, and it seems many are getting
it to work, atleast maybe it will work on the new. And if mainline does
maxjitter/latency below 0.2ms on the new machine, which will be very
specifically tuned for low latency hardware-wise, I ofcourse don`t need
rt, unless there should be an argument of better performance still, which
most seem to think there isn`t.
So anyway down to 0.2ms is where I care. I think. Great job on doing RT
though, but unfortunately it hasn`t worked here. Actually I could try a
live RT distro, on my mac mini also. :)
Peace Be With You.
next prev parent reply other threads:[~2012-10-27 9:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 21:45 [ANNOUNCE] 3.6.2-rt4 Uwaysi Bin Kareem
2012-10-26 21:54 ` Paul Gortmaker
2012-10-26 22:24 ` Uwaysi Bin Kareem
2012-10-27 0:17 ` Sven-Thorsten Dietrich
2012-10-27 9:41 ` Uwaysi Bin Kareem
2012-10-27 9:50 ` Uwaysi Bin Kareem [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-29 20:39 Ove Karlsen
2012-10-20 19:40 Thomas Gleixner
2012-10-22 21:54 ` Paul Gortmaker
[not found] ` <op.wmk8f6m96426ze@localhost.localdomain>
[not found] ` <alpine.LFD.2.02.1210222029480.2756@ionos>
2012-10-22 21:05 ` Uwaysi Bin Kareem
2012-10-23 6:52 ` Thomas Gleixner
2012-10-23 22:53 ` Uwaysi Bin Kareem
2012-10-24 5:01 ` Sven-Thorsten Dietrich
2012-10-24 8:16 ` Uwaysi Bin Kareem
2012-10-24 9:59 ` Thomas Gleixner
2012-10-24 10:48 ` Uwaysi Bin Kareem
2012-10-24 14:27 ` Thomas Gleixner
2012-10-24 17:06 ` Uwaysi Bin Kareem
2012-10-24 18:38 ` Thomas Gleixner
2012-10-24 18:47 ` Uwaysi Bin Kareem
2012-10-24 19:24 ` Thomas Gleixner
2012-10-24 19:32 ` Uwaysi Bin Kareem
2012-10-24 19:49 ` Thomas Gleixner
2012-10-24 19:57 ` Uwaysi Bin Kareem
2012-10-25 21:21 ` Thomas Gleixner
2012-10-26 14:24 ` Paul Gortmaker
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=op.wmt0antg6426ze@millennium.getinternet.no \
--to=uwaysi.bin.kareem@paradoxuncreated.com \
--cc=linux-rt-users@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 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.