From: Martin Konold <martin.konold@erfrakon.de>
Organization: erfrakon
To: Timo Sirainen <tss@iki.fi>
Subject: Re: Lockless file reading
Date: Thu, 28 Aug 2003 11:48:39 +0200
User-Agent: KMail/kroupware-1.0.0
References: <3217CEE6-D906-11D7-A165-000393CC2E90@iki.fi> <200308281113.59112.martin.konold@erfrakon.de> <1062062858.1454.254.camel@hurina>
In-Reply-To: <1062062858.1454.254.camel@hurina>
Cc: linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200308281148.39515.martin.konold@erfrakon.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1176
Lines: 34

Am Thursday 28 August 2003 11:27 am schrieben Sie:

Hi,

> It's not about CPU usage. It's mostly about being able to modify the
> file even when there's thousands of simultaneous readers that could
> otherwise keep the file locked almost constantly.

No, the readers only have to check if the file got locked by the writer(s).
  
> Also it'd be nice to support NFS with .lock files since no-one really
> uses lockd.

IMHO a lock file on nfs is the most inefficient locking mechanism in case of 
readers and writer(s) on the same machine.

BTW: What about moving this thread away from linux-kernel? It is already clear 
that the kernel does not provide these guarantees you asked for.

Regards,
-- martin

Dipl.-Phys. Martin Konold
e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Nobelstrasse 15, 70569 Stuttgart, Germany
fon: 0711 67400963, fax: 0711 67400959
email: martin.konold@erfrakon.de

-
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/