Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262455AbTH0Xji (ORCPT ); Wed, 27 Aug 2003 19:39:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262474AbTH0Xji (ORCPT ); Wed, 27 Aug 2003 19:39:38 -0400 Received: from mail.jlokier.co.uk ([81.29.64.88]:19846 "EHLO mail.jlokier.co.uk") by vger.kernel.org with ESMTP id S262455AbTH0Xjh (ORCPT ); Wed, 27 Aug 2003 19:39:37 -0400 Date: Thu, 28 Aug 2003 00:39:03 +0100 From: Jamie Lokier To: Timo Sirainen Cc: root@chaos.analogic.com, Martin Konold , linux-kernel@vger.kernel.org Subject: Re: Lockless file reading Message-ID: <20030827233903.GB3759@mail.jlokier.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 679 Lines: 16 Timo Sirainen wrote: > Maybe it would be possible to use some kind of error detection > checksums which would guarantee that the data either is valid or isn't, > regardless of the order in which it is written. I don't really know how > that could be done though. You can use a strong checksum like MD5, if that is really faster than locking. (Over NFS it probably is faster than fcntl()-locking, for small data blocks). -- Jamie - 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/