From owner-freebsd-arch Mon May 15 11:26:24 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id E4F8737B655; Mon, 15 May 2000 11:25:57 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA13075; Mon, 15 May 2000 11:26:26 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005151826.LAA13075@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Hibma Cc: Mike Smith , Doug Rabson , arch@freebsd.org Subject: Re: A new api for asynchronous task execution In-reply-to: Your message of "Mon, 15 May 2000 11:20:32 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 May 2000 11:26:26 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We have a number of different callout list implementation kicking around > > in the kernel at the moment; > > > > - the EVENTHANDLER stuff > > - the optimised callout list handling in kern_timeout.c > > - a few ad-hoc leftovers like config_intrhook that should have been > > EVENTHANDLERed but weren't > > - The delayed attach for disk devices > - The after interrupts-have-been-switched-on task queue Er, that's config_intrhook. > None of these need any functionality above the provided stuff. That's not true; several users of the above require the ability to be sorted onto their task queue. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message