From owner-freebsd-arch Tue Jan 21 20:49: 2 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C71CD37B401 for ; Tue, 21 Jan 2003 20:49:01 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B8C243F13 for ; Tue, 21 Jan 2003 20:49:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.6/8.12.6) with ESMTP id h0M4mv0i000622; Tue, 21 Jan 2003 20:48:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.6/8.12.6/Submit) id h0M4mvMh000621; Tue, 21 Jan 2003 20:48:57 -0800 (PST) Date: Tue, 21 Jan 2003 20:48:57 -0800 (PST) From: Matthew Dillon Message-Id: <200301220448.h0M4mvMh000621@apollo.backplane.com> To: "M. Warner Losh" Cc: bright@mu.org, sam@errno.com, arch@FreeBSD.ORG Subject: Re: Alfre's malloc changes: the next step References: <072d01c2c1a7$0fbba490$52557f42@errno.com> <20030121.165125.29485504.imp@bsdimp.com> <20030122002340.GK42333@elvis.mu.org> <20030121.192436.65876718.imp@bsdimp.com> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Would making the malloc flags an enum and the mbuf flags another enum be sufficient to catch API crossover problems at compile time? For the record, I like the idea of a mandatory M_WAIT or M_NOWAIT, not because it's good design theory, but because this particular interface has been misused so often that we really have to make it explicit. But we shouldn't panic in this case, instead we should printf() (else third party modules may create unecessary crashes for the next couple of years). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message