Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 28 Oct 2002 09:22:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 28 Oct 2002 09:22:57 -0500 Received: from delta.ds2.pg.gda.pl ([213.192.72.1]:33760 "EHLO delta.ds2.pg.gda.pl") by vger.kernel.org with ESMTP id ; Mon, 28 Oct 2002 09:22:56 -0500 Date: Mon, 28 Oct 2002 15:28:48 +0100 (MET) From: "Maciej W. Rozycki" Reply-To: "Maciej W. Rozycki" To: Andi Kleen cc: Jamie Lokier , eggert@twinsun.com, linux-kernel@vger.kernel.org Subject: Re: nanosecond file timestamp resolution in filesystems, GNU make, etc. In-Reply-To: <20021028151533.D18441@wotan.suse.de> Message-ID: Organization: Technical University of Gdansk MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 997 Lines: 23 On Mon, 28 Oct 2002, Andi Kleen wrote: > > So I propose: add a field to struct stat indicating the resolution of > > the timestamps in it. It can go on the end. > > It's impossible. There is no space left in struct stat64 > And adding a new syscall just for that would be severe overkill. Well, possibly more stuff could benefit from new stat syscalls, like a st_gen member for inode generations. And as someone suggested, a version number or a length could be specified by the calls this time to permit less disturbing expansion in the future. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available + - 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/