Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264249AbTH1Vtg (ORCPT ); Thu, 28 Aug 2003 17:49:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264295AbTH1Vtg (ORCPT ); Thu, 28 Aug 2003 17:49:36 -0400 Received: from quechua.inka.de ([193.197.184.2]:16605 "EHLO mail.inka.de") by vger.kernel.org with ESMTP id S264249AbTH1VtO (ORCPT ); Thu, 28 Aug 2003 17:49:14 -0400 From: Bernd Eckenfels To: linux-kernel@vger.kernel.org Subject: Re: Lockless file reading In-Reply-To: <20030828121823.GB6800@mail.jlokier.co.uk> X-Newsgroups: ka.lists.linux.kernel User-Agent: tin/1.5.19-20030610 ("Darts") (UNIX) (Linux/2.4.20-xfs (i686)) Message-Id: Date: Thu, 28 Aug 2003 23:49:06 +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 793 Lines: 19 In article <20030828121823.GB6800@mail.jlokier.co.uk> you wrote: > The kernel does not provide synchronisation between read() and write() > data transfers, and it does not always use atomic 32-bit reads and > writes either. There are some gurantees for pipes, for example. Writes which are smaller than pathconf(_PC_PIPE_BUF, pipe) will be atomic, i.e. not mixed between multiple writers. I dont know what the gurantee for write/read or mmap is. Greetings Bernd -- eckes privat - http://www.eckes.org/ Project Freefire - http://www.freefire.org/ - 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/