From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 21 04:05:56 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CDEF37B408 for ; Mon, 21 Apr 2003 04:05:56 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30A2B43F75 for ; Mon, 21 Apr 2003 04:05:53 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (foem [10.11.0.2])h3LB5qAf033040 for ; Mon, 21 Apr 2003 13:05:52 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Mon, 21 Apr 2003 13:05:52 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem.leiden.webweaving.org To: freebsd-hackers@freebsd.org Message-ID: <20030421130029.A29555-100000@foem.leiden.webweaving.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: wi(4) - polling(4) changes / DEVICE_POLLING X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2003 11:05:57 -0000 Is anyone actively working on making the polling(8) to the wi(4) driver ? As in www.wirelessleiden.nl we're seeing very significant (>80%) INTR time spend when doing simple bridging from one wi(4) card to another on the lower end motherboards (P1, slow P2's). And we have similarly seen that using DEVICE_POLLING on the sis(4) cards in the same device would instantly drop sis0<->sis1 INTR time resources to acceptible levels (and increase performance by almost a 2 fold). Or are there any fundamental issues with making wi(4) polling(4) aware ? I.e. some specific firmware issues, etc ? Thanks ! Dw