From: Ove Karlsen <ove.karlsen@paradoxuncreated.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Compilation options (for low jitter)
Date: Sun, 28 Oct 2012 13:10:05 +0100 [thread overview]
Message-ID: <508D209D.8060003@paradoxuncreated.com> (raw)
In-Reply-To: <508D1EBE.5070601@paradoxuncreated.com>
Today I actually switched to Thunderbird.
Anyway disabling no_sse2 was a bad idea, increasing jitter/overhead.
Some optimizations for low-jitter such as no_defer and prefech latency
can change percieved latency/jitter slighty.
http://paradoxuncreated.com/Blog/wordpress/?p=4223
And I am always interested in more information on that.
Currently I am using "-O3 -fno-defer-pop --param prefetch-latency=100"
parent reply other threads:[~2012-10-28 12:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <508D1EBE.5070601@paradoxuncreated.com>]
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=508D209D.8060003@paradoxuncreated.com \
--to=ove.karlsen@paradoxuncreated.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
Powered by JetHome