Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Sep 2006 14:03:50 -0700
From:      David G Lawrence <dg@dglawrence.com>
To:        Peter Jeremy <peterjeremy@optushome.com.au>
Cc:        freebsd-stable@freebsd.org, Oliver Brandmueller <ob@e-Gitt.NET>, John Baldwin <jhb@freebsd.org>
Subject:   Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2
Message-ID:  <20060927210349.GG14975@tnn.dglawrence.com>
In-Reply-To: <20060927191402.GB932@turion.vk2pj.dyndns.org>
References:  <451A1375.5080202@gneto.com> <20060927071538.GF22229@e-Gitt.NET> <451A4189.5020906@samsco.org> <20060927152824.GJ22229@e-Gitt.NET> <20060927155553.GB14563@icarus.home.lan> <20060927155904.GM22229@e-Gitt.NET> <451AA7B1.5080202@samsco.org> <20060927191402.GB932@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> In the past (RELENG_5) I've had major problems with syncer delaying
> interrupt threads for long periods (I've seen 8msec).  See
> http://lists.freebsd.org/pipermail/freebsd-stable/2005-February/012346.html
> I'm not sure if this is still a problem (but I am still having some
> problems which may be caused by excessive interrupt and will be doing
> some debugging as I get time).
...
> tool and then post-process the file looking for oddities.  In my case,
> there was a _very_ high correlation between long latencies and syncer.
> If anyone's interested in this approach, I can provide the relevant
> code diffs.

   I've seen this problem as well - results in around 9-10ms of occasional
scheduling delay for a real-time streaming application that I'm developing.
Shutting off softupdates on all of the mounted filesystems helps.
   Note that the watchdog timeout for the network drivers is usually 8000ms
(8 seconds), so this is unlikely to be related to that problem.

-DG

David G. Lawrence
President
Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500
The FreeBSD Project - http://www.freebsd.org
Pave the road of life with opportunities.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060927210349.GG14975>