From owner-freebsd-arch Wed May 24 20:36:29 2000 Delivered-To: freebsd-arch@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1A19137BDCA for ; Wed, 24 May 2000 20:36:26 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA75463; Wed, 24 May 2000 20:38:21 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: Chuck Paterson , arch@FreeBSD.ORG Subject: Re: Short summary In-reply-to: Your message of "Wed, 24 May 2000 19:03:55 PDT." <200005250203.TAA78162@apollo.backplane.com> Date: Wed, 24 May 2000 20:38:21 -0700 Message-ID: <75460.959225901@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The one problem with this concept is that there is no easy migration > path getting from SPL ops to Mutex ops, because an SPL op currently > involves a bitmask of several interrupts rather then a single interrupt. > Thus the SPL ops would translate into several mutexes rather then a > single mutex and wind up being *very* expensive for the period of time > it takes us to then move onto the next step (collapsing them into single > mutexes again). We were looking for an easier migration path in > order to try to keep the kernel runnable for the month or two (or > longer) it would require to get everything straightened out. I think it's also fair to say that we'd be willing to accept a certain period of outright breakage in FreeBSD-current if it gets us to the right place, e.g. a painless transition is not necessarily the goal so much as getting things done right. We've gone through similar periods with -current in the past and nobody had too much difficultly with the concept provided that we ANNOUNCED it well in advance and told the cvsuppers to basically turn their cron jobs off or elect not to try and build the world until the tree was declared safe again. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message