From owner-freebsd-current@FreeBSD.ORG Tue Aug 28 11:45:44 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0723106566C; Tue, 28 Aug 2012 11:45:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id A59A78FC18; Tue, 28 Aug 2012 11:45:44 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 08266B93B; Tue, 28 Aug 2012 07:45:44 -0400 (EDT) From: John Baldwin To: lev@freebsd.org Date: Tue, 28 Aug 2012 07:44:23 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <135297243.20120827061957@serebryakov.spb.ru> <201208271226.03496.jhb@freebsd.org> <1758728845.20120828004713@serebryakov.spb.ru> In-Reply-To: <1758728845.20120828004713@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201208280744.23419.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 28 Aug 2012 07:45:44 -0400 (EDT) Cc: freebsd-current@freebsd.org Subject: Re: What is "Fast task queue"? (Was: How to understand what `swi5' kernel thread does?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2012 11:45:44 -0000 On Monday, August 27, 2012 4:47:13 pm Lev Serebryakov wrote: > Hello, John. > You wrote 27 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., 20:= 26:03: >=20 > >> What "fast tasks" are performed via this queue? Under network load it > >> is main consumer of CPU. > JB> Certain NIC drivers perform much of their interrupt handling in that= =20 thread. > Yep, I've found, that my if_vr uses it. One more question: does ipfw > rules works in same thread? I have ``net.isr.dispatch=3D"direct"'' set. Yes, with the default setting of direct dispatch, all of the receive side of the network stack runs in the driver's interrupt handler. In the case of vr(4) that would be in this thread. =2D-=20 John Baldwin