From: "sufcrusher" <sufcrusher@zonnet.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Low latency on large uploads - almost done but not quite.
Date: Wed, 18 Jun 2003 19:10:59 +0000 [thread overview]
Message-ID: <marc-lartc-105596369429003@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105560610320685@msgid-missing>
You couldn't even if you wanted. High res timer requeres at least one of the
faster pentiums (not all pentiums can do it).
If you can't get a stable latency in the end, it might be worthwhile to
upgrade to a pentium, but for now I'd keep trying some finetuning.
Jannes Faber
----- Original Message -----
From: "Thilo Schulz" <arny@ats.s.bawue.de>
To: <lartc@mailman.ds9a.nl>
Sent: Wednesday, June 18, 2003 2:32 PM
Subject: Re: [LARTC] Low latency on large uploads - almost done but not
quite.
On Tuesday 17 June 2003 20:16, sufcrusher wrote:
> Also make sure you patched the kernel to use the high resolution timer
> (info at www.docum.org somewhere). That helped a lot in my case (you can
> put the ceilingrates closer to the actual 128kbit and therefore reduce
> latency as well). I'm not sure it's still necessary on 2.4.20 and/or
> 2.4.21.
I have a 133 Mhz AMD 486 - whether setting the resolution timer up would be
very good for performance I don't know.
- Thilo Schulz
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-06-18 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 15:54 [LARTC] Low latency on large uploads - almost done but not quite Thilo Schulz
2003-06-15 9:09 ` Stef Coene
2003-06-15 11:44 ` Thilo Schulz
2003-06-15 12:00 ` Stef Coene
2003-06-16 7:54 ` [LARTC] Low latency on large uploads - almost done but not Corey Rogers
2003-06-17 18:16 ` [LARTC] Low latency on large uploads - almost done but not quite sufcrusher
2003-06-18 12:32 ` Thilo Schulz
2003-06-18 19:10 ` sufcrusher [this message]
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=marc-lartc-105596369429003@msgid-missing \
--to=sufcrusher@zonnet.nl \
--cc=lartc@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.