From owner-p4-projects@FreeBSD.ORG Tue Aug 1 19:31:10 2006 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 9C85D16A4E5; Tue, 1 Aug 2006 19:31:10 +0000 (UTC) X-Original-To: perforce@freebsd.org Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 725FC16A4DE; Tue, 1 Aug 2006 19:31:10 +0000 (UTC) (envelope-from flag@newluxor.wired.org) Received: from mail.oltrelinux.com (krisma.oltrelinux.com [194.242.226.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 036F743D69; Tue, 1 Aug 2006 19:31:09 +0000 (GMT) (envelope-from flag@newluxor.wired.org) Received: from newluxor.wired.org (ip-115-167.sn1.eutelia.it [62.94.115.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.oltrelinux.com (Postfix) with ESMTP id C453611B254; Tue, 1 Aug 2006 21:31:08 +0200 (CEST) Received: (from flag@localhost) by newluxor.wired.org (8.13.7/8.13.7/Submit) id k71JTYxu035085; Tue, 1 Aug 2006 21:29:34 +0200 (CEST) (envelope-from flag) Date: Tue, 1 Aug 2006 21:29:28 +0200 From: Paolo Pisati To: Sam Leffler Message-ID: <20060801192928.GA34484@tin.it> References: <200608011725.k71HP4ol019342@repoman.freebsd.org> <44CF928B.7020102@errno.com> <200608011434.07440.jhb@freebsd.org> <44CFA3DB.2090801@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44CFA3DB.2090801@errno.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at krisma.oltrelinux.com Cc: Sam Leffler , Perforce Change Reviews , John Baldwin Subject: Re: PERFORCE change 102954 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2006 19:31:10 -0000 On Tue, Aug 01, 2006 at 11:56:27AM -0700, Sam Leffler wrote: > Basically yes, the stuff run in the private taskq thread should run in > the deferred interrupt context. The only issue is how to handle beacon > processing (and in the future UAPSD processing). I'm not familiar with > what's allowed to run in a filter routine but deferring the beacon frame > generation is likely not going to work and the work done to post a > beacon frame may do calls that are not permitted. a filter handler is just like a fast handler returning a value. BTW i see many calls from ath_intr() to the blob hal interface, are those functions blocking? bye -- Paolo Piso's first law: nothing works as expected!