From owner-freebsd-arch@FreeBSD.ORG Fri Aug 1 23:06:12 2003 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 B5C8C37B401 for ; Fri, 1 Aug 2003 23:06:12 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E411E43FBF for ; Fri, 1 Aug 2003 23:06:11 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 8639 invoked from network); 2 Aug 2003 06:06:10 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 2 Aug 2003 06:06:10 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sat, 2 Aug 2003 01:04:09 -0500 (CDT) From: Mike Silbersack To: arch@freebsd.org Message-ID: <20030801235716.T2165@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Another 4.x ABI question; uidinfo 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: Sat, 02 Aug 2003 06:06:13 -0000 Ok, so I took another at the uidinfo ui_ref field being only a u_short in 4.x. As I recall, the reason this was not changed to a u_int was binary compatibility... however, as I look around the source tree, it appears that the only places uidinfos are used are within kern/, and then generally only by things touching procs. Thirdly, it appears that the refcount is only modified within three functions in kern_resource.c, and that ui_ref is the last member in that structure. So, is there _really_ a problem in promoting ui_ref to an int from a short? As far as I can tell, any network or sound driver should be completely insulated from such a change; do we have any other class of binary modules to worry about? Thanks, Mike "Silby" Silbersack