From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23756 invoked by alias); 27 Nov 2003 09:12:55 -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 23749 invoked from network); 27 Nov 2003 09:12:54 -0000 Received: from unknown (HELO melelios.dmz.elios-informatique.fr) (194.250.150.132) by sources.redhat.com with SMTP; 27 Nov 2003 09:12:54 -0000 Received: from figuier ([192.168.7.116]) by melelios.dmz.elios-informatique.fr with Microsoft SMTPSVC(5.0.2195.5329); Thu, 27 Nov 2003 10:19:41 +0100 From: "Vincent Catros" To: "'David Woodhouse'" Cc: Date: Thu, 27 Nov 2003 09:12:00 -0000 Message-ID: <000001c3b4c7$023894e0$7407a8c0@figuier> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: <1069892845.14994.47.camel@imladris.demon.co.uk> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-OriginalArrivalTime: 27 Nov 2003 09:19:41.0593 (UTC) FILETIME=[96AD3090:01C3B4C7] Subject: [ECOS] RE : [ECOS] Is JFFS2 thread-safe? X-SW-Source: 2003-11/txt/msg00414.txt.bz2 Hello David, And thank you for your answer. > -----Message d'origine----- > De=A0: David Woodhouse [mailto:dwmw2@infradead.org] > Envoy=E9=A0: jeudi 27 novembre 2003 01:27 > =C0=A0: Vincent Catros > Cc=A0: ecos-discuss@sources.redhat.com > Objet=A0: Re: [ECOS] Is JFFS2 thread-safe? >=20 [...] > The core JFFS2 code is thread safe, assuming the Linux semaphore and > spinlock primitives are correctly translated into eCos mutexes and > preemption blocks. The bit that I haven't paid much attention to w.r.t. > locking is the inode cache handling in fs-ecos.c. >=20 > In fact, I suspect that is actually OK because we set the > CYG_SYNCMODE_FILE_FILESYSTEM flag and hence the fileio layer ensures > that only one file system method is invoked at a time. It would be > better to do our own locking and drop that flag though, since it makes > coordinating the locking with gcthread.c a little nicer. [...] If I understand, JFFS2 should be thread safe, but this has never been tested since multual access is avoided by fileio layer when using CYG_SYNCMODE_FILE_FILESYSTEM flag? Am I wrong? Regards. Vincent -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss