Date: Tue, 22 Nov 2005 13:39:05 -0500 From: John Baldwin <jhb@freebsd.org> To: "Konstantin Prokazoff" <kprokazov@svr.kiev.ua> Cc: freebsd-hackers@freebsd.org Subject: Re: poll()/select() Message-ID: <200511221339.06731.jhb@freebsd.org> In-Reply-To: <0d4801c5ef45$d09ba3d0$0c02010a@svr012> References: <3.0.1.32.20051121044201.00aa1490@pop.redshift.com> <200511211038.26937.jhb@freebsd.org> <0d4801c5ef45$d09ba3d0$0c02010a@svr012>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 22 November 2005 04:19 am, Konstantin Prokazoff wrote: > Welcome, > > John, thanks for the answer. I'll test today bus_setup_intr() without > INTR_FAST flag, but how I remember, this cause to system heavy load for > interrupt processing ;( in my case. > My handler uses spin mutexes to block inter-interrupting & sleep > mutexes to block some structures now. I have tried to use swi/taskqueue, > but result is a "sync" degradation level. > Can you help with sources briefing in my driver case? > Thnx in advance. Well, I'm not quite sure what you mean by "sync" degradation level for starters, but I'm not much an expert on synchronous serial devices. What kind of load are you seeing on your system with the non-INTR_FAST handler? And what kind of system (CPU, etc.) are you running FreeBSD on? > > > I have this situation cause to INTR_FAST interrupt handler in > > > device driver for Digium's PCI board, which provides 4 T1/E1 > > > interfaces. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511221339.06731.jhb>