From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4083 invoked by alias); 28 Nov 2003 11:09:05 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 4051 invoked from network); 28 Nov 2003 11:09:04 -0000 Received: from unknown (HELO pentafluge.infradead.org) (213.86.99.235) by sources.redhat.com with SMTP; 28 Nov 2003 11:09:04 -0000 Received: from fish.redhat.com ([213.86.99.237] helo=[172.16.18.64]) by pentafluge.infradead.org with asmtp (Exim 4.22 #5 (Red Hat Linux)) id 1APgWC-0003ez-H6; Fri, 28 Nov 2003 11:10:36 +0000 From: David Woodhouse To: Vincent Catros Cc: ecos-discuss@sources.redhat.com In-Reply-To: <000e01c3b508$b6f34d30$7407a8c0@figuier> References: <000e01c3b508$b6f34d30$7407a8c0@figuier> Content-Type: text/plain Message-Id: <1070017743.10048.22.camel@hades.cambridge.redhat.com> Mime-Version: 1.0 Date: Fri, 28 Nov 2003 11:09:00 -0000 Content-Transfer-Encoding: 7bit X-SA-Exim-Mail-From: dwmw2@infradead.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Pentafluge-Mail-From: Subject: [ECOS] Re: RE : [ECOS] Is JFFS2 thread-safe? X-SW-Source: 2003-11/txt/msg00423.txt.bz2 On Thu, 2003-11-27 at 18:05 +0100, Vincent Catros wrote: > But it seems that read() and write() lead to a cyg_file_lock which call > cyg_fs_lock (see fd.cxx). > > So, read() and write() are probably serialized to. Yes, they do seem to be serialised, since we have CYG_SYNCMODE_IO_FILESYSTEM set. That shouldn't be needed. All we need is CYG_SYNCMODE_IO_FILE, to ensure that large writes appear atomic to other simultaneous readers. -- dwmw2 -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss