Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 5 Oct 2001 10:38:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 5 Oct 2001 10:38:50 -0400 Received: from ns.suse.de ([213.95.15.193]:42505 "HELO Cantor.suse.de") by vger.kernel.org with SMTP id ; Fri, 5 Oct 2001 10:37:39 -0400 Date: Fri, 5 Oct 2001 16:38:07 +0200 From: Andi Kleen To: Padraig Brady Cc: Andi Kleen , Alex Larsson , Ulrich Drepper , linux-kernel@vger.kernel.org Subject: Re: Finegrained a/c/mtime was Re: Directory notification problem Message-ID: <20011005163807.A13524@gruyere.muc.suse.de> In-Reply-To:

<20011003232609.A11804@gruyere.muc.suse.de> <3BBDAB24.7000909@antefacto.com> <20011005150144.A11810@gruyere.muc.suse.de> <3BBDB26D.2050705@antefacto.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BBDB26D.2050705@antefacto.com>; from padraig@antefacto.com on Fri, Oct 05, 2001 at 02:15:25PM +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > >Another advantage of using the real time instead of a counter is that > >you can easily merge the both values into a single 64bit value and do > >arithmetic on it in user space. With a generation counter you would need > >to work with number pairs, which is much more complex. > > > ?? > if (file->mtime != mtime || file->gen_count != gen_count) > file_changed=1; And how would you implement "newer than" and "older than" with a generation count that doesn't reset in a always fixed time interval (=requiring additional timestamps in kernel)? -Andi - 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/