From owner-freebsd-arch Wed May 17 10:58: 3 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 6C6B437BC74; Wed, 17 May 2000 10:58:00 -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 KAA07014; Wed, 17 May 2000 10:58:43 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005171758.KAA07014@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Terry Lambert Cc: dfr@nlsystems.com (Doug Rabson), msmith@FreeBSD.ORG (Mike Smith), n_hibma@calcaphon.com (Nick Hibma), arch@FreeBSD.ORG Subject: Re: A new api for asynchronous task execution In-reply-to: Your message of "Wed, 17 May 2000 17:45:44 -0000." <200005171745.KAA06412@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 May 2000 10:58:42 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I do hope to be able to replace at least some of these pieces. I like the > > idea of a priority sorted list of tasks, probably using a priority field > > in struct task. > > Bletch. > > This is a job best handled by managing insertion order, rather than > by way of an explicit sort. Insertion order also keeps the structure > both small and generic. You specifically can't "manage insertion order", which is why the queues need to be sorted. Go look at the current problem set before making sweeping assertions like this. -- \\ 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