Date: Fri, 28 Oct 2005 21:58:42 +0800 From: Dinesh Nair <dinesh@alphaque.com> To: Scott Long <scottl@samsco.org> Cc: freebsd-hackers@freebsd.org Subject: Re: locking in a device driver Message-ID: <43622E92.2070205@alphaque.com> In-Reply-To: <4360DD7B.20900@samsco.org> References: <435EEC56.9080708@samsco.org> <200510261130.45506.jhb@freebsd.org> <435FA6A9.4000600@samsco.org> <200510261324.03790.jhb@freebsd.org> <4360B8EE.4070605@alphaque.com> <4360DD7B.20900@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/27/05 22:00 Scott Long said the following: > If you need to protect your pseudodriver from being interrupted by the > real driver then you'll need to use the same spl() as the driver. Note > that you shouldn't be using splhigh() unless you really know what you the driver currently is set to use INTR_TYPE_MISC, which from my understanding can only be masked with splhigh(). using another INTR_TYPE may be possible, so this is something i can explore. however, the device interrupts at a constant 1000Hz, as it's a quad-span E1/T1 line card, and thus it needs to have that interrupt serviced pronto to avoid E1/T1 frame slips. any advice here ? -- Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43622E92.2070205>