From owner-freebsd-current@FreeBSD.ORG Thu Oct 9 03:20:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ECBA16A4B3 for ; Thu, 9 Oct 2003 03:20:03 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9A8743FB1 for ; Thu, 9 Oct 2003 03:20:01 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfl87.dialup.mindspring.com ([165.247.213.7] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1A7Xtj-0006r4-00; Thu, 09 Oct 2003 03:19:56 -0700 Message-ID: <3F8535F6.36957D17@mindspring.com> Date: Thu, 09 Oct 2003 03:18:30 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Michael O. Boev" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4e6b0fc5ca0c618a1fe0c62f5fdacee64666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@FreeBSD.ORG Subject: Re: Why is em nic generating interrupts? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 09 Oct 2003 10:20:03 -0000 "Michael O. Boev" wrote: > I've got a [uniprocessor 5.1-RELEASE] router machine with fxp and em nics. > I've built my kernel with the following included: > > options DEVICE_POLLING > options HZ=2500 > > and enabled polling in /etc/sysctl.conf. [ ... ] > What's happening? Is polling working in my case? > If yes, why is vmstat showing interrupts? I see clearly, > that fxp's counter doesn't increase, and em's is constantly growing. > > Is there anyone who knows for sure that em's polling works? You may want to ask Luigi; polling is his code. However, I believe the issue is that polling doesn't start until you take an interrupt, and it stops as soon as there is no more data to process, and waits for the next interrupt. If you were to jack your load way up, you would probably see an increase in interrupts, then them dropping off dramatically. If all else fails, read the source code... 8-). -- Terry