Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Mar 2003 17:55:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Mar 2003 17:55:55 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:2828 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 20 Mar 2003 17:55:51 -0500 Message-ID: <3E7A4977.5090700@zytor.com> Date: Thu, 20 Mar 2003 15:06:31 -0800 From: "H. Peter Anvin" Organization: Zytor Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211 X-Accept-Language: en, sv MIME-Version: 1.0 To: Joel Becker CC: linux-kernel@vger.kernel.org Subject: Re: Larger dev_t and major/minor split References: <20030320220901.GR2835@ca-server1.us.oracle.com> In-Reply-To: <20030320220901.GR2835@ca-server1.us.oracle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 713 Lines: 21 Joel Becker wrote: > On Thu, Mar 20, 2003 at 01:42:41PM -0800, H. Peter Anvin wrote: > >>b) In order to support NFSv2 and other filesystems which only support >> a 32-bit dev_t, I suggest we stay within a (12,20)-bit range for as > > > Hmm, I guess that means dropping ext2/3 for / ;-( > Last I checked, all traditional (inode-based) Unix filesystems, including ext2/3 used block pointers for dev_t. There are plenty of block pointers; 60 bytes worth. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/