From owner-freebsd-smp Mon Dec 18 15:50:29 2000 From owner-freebsd-smp@FreeBSD.ORG Mon Dec 18 15:50:26 2000 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 1827D37B400 for ; Mon, 18 Dec 2000 15:50:26 -0800 (PST) Received: from marakesh-16.budapest.interware.hu ([195.70.50.144] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 148A2i-0004JA-00; Tue, 19 Dec 2000 00:50:08 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A3EA281.7330E8CF@elischer.org> Date: Mon, 18 Dec 2000 15:49:21 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Chuck Paterson Cc: smp@FreeBSD.ORG Subject: Re: Netgraph locking primatives. take 1. References: <200012182257.eBIMvgP24201@berserker.bsdi.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chuck Paterson wrote: > > }Chuck Paterson wrote: > }> > }> Julian > }> Is there some other mechanism to insure that the code > }> which knows about the queue on which the packet is queued doesn't > }> go away while the packet is on queued? I thought this was > }> part of what was being solved, but may just not understand. > }> > }> Chuck > } > }Sorry I don;t quite understand the question.. > } > > You talked about various nodes before, such as node X, and > node Y. Presumably node X and the code that knows about it, and > its queues could go away totally. I thought, perhaps wrongly, that > this mechanism was going to be used to solve this problem > also. ah yes.. the node removal message is obviously a writer. part of it's job is to drain and remove the queue. (the message is sent to the node but it's handled by the framework) teh module that supplies the code that is running the node cannot be unloaded until thre are no more nodes of that type, and the node cannot be shutdown until it has exclusive access to the node via a write lock, (but is running code in teh framework rather than code from the module, so we know at that stage that no processor is running any code from teh module, and we can remove it.. > > }BTW BSDi is rejecting my mail to you as spam and I can't figure out why... > }Just as well you are on the lists. > }(it goes via my ISPs mail server, not direct from the dialup) > } > > As far as I can tell the mail filters we (BSDi) use just suck > wind. > > } > }-- > } __--_|\ Julian Elischer > } / \ julian@elischer.org > } ( OZ ) World tour 2000 > }---> X_.---._/ presently in: Budapest > } v > } > } > > Chuck -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message