From owner-freebsd-arch@FreeBSD.ORG Mon Mar 15 07:43:47 2004 Return-Path: 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 6D69316A4CE for ; Mon, 15 Mar 2004 07:43:47 -0800 (PST) Received: from darkness.comp.waw.pl (unknown [195.117.238.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0650343D1D for ; Mon, 15 Mar 2004 07:43:47 -0800 (PST) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 3808BAC974; Mon, 15 Mar 2004 16:43:46 +0100 (CET) Date: Mon, 15 Mar 2004 16:43:46 +0100 From: Pawel Jakub Dawidek To: Dag-Erling Sm?rgrav Message-ID: <20040315154346.GD8930@darkness.comp.waw.pl> References: <20040315143123.GB8930@darkness.comp.waw.pl> <20040315150248.GL35475@elvis.mu.org> <20040315153919.GC8930@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9UV9rz0O2dU/yYYn" Content-Disposition: inline In-Reply-To: <20040315153919.GC8930@darkness.comp.waw.pl> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: freebsd-arch@freebsd.org Subject: Re: Bitstring(9) in kernel. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 15:43:47 -0000 --9UV9rz0O2dU/yYYn Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 15, 2004 at 04:39:19PM +0100, Pawel Jakub Dawidek wrote: +> On Mon, Mar 15, 2004 at 04:10:12PM +0100, Dag-Erling Sm?rgrav wrote: +> +> That being said, I have no objection to Pawel's patch. +>=20 +> Just want to double check: Should I go ahead and commit it? +> Or you want think this over? +>=20 +> The only user- and kernel-land friendly solution will be to +> reimplement bit_alloc() as bit_alloc(bits, type, flags). +> Arguments 'type' and 'flags' will be unused in userland and for +> userland-only application we can provide bit_ualloc(bits) +> or something. But this looks a bit hackish. No, maybe just create bit_malloc(bits, type, flags) and don't touch bit_alloc() for backwards compatibility. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --9UV9rz0O2dU/yYYn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAVc8yForvXbEpPzQRArDkAJwLQOMY2yabBoi1HA3XKdkhSEE1QQCcDFri 3rrxmtp7sN5QpoWQ6lETQ0U= =e55N -----END PGP SIGNATURE----- --9UV9rz0O2dU/yYYn--