This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RE : Is JFFS2 thread-safe?

From: David Woodhouse <dwmw2 at infradead dot org>
To: Gary Thomas <gary at mlbassoc dot com>
Cc: Vincent Catros <vincent dot catros at elios-informatique dot fr>, ecos-discuss at sources dot redhat dot com
Date: Sat, 29 Nov 2003 15:46:12 +0000
Subject: Re: [ECOS] RE : [ECOS] Is JFFS2 thread-safe?
References: <000001c3b4c7$023894e0$7407a8c0@figuier> <1070018075.10048.29.camel@hades.cambridge.redhat.com> <1070018876.10048.35.camel@hades.cambridge.redhat.com> <1070035746.13188.17.camel@hades.cambridge.redhat.com> <33052.63.173.215.14.1070117670.squirrel@www.chez-thomas.org>

On Sat, 2003-11-29 at 07:54 -0700, Gary Thomas wrote:
> What do you mean?  If the scheduler lock is non-zero, then no
> scheduling takes place (certainly in the single processor case)

Er, but what causes the scheduler lock to become non-zero when I lock a
spinlock?

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

References:
- RE : Is JFFS2 thread-safe?
  - From: Vincent Catros
- Re: RE : Is JFFS2 thread-safe?
  - From: David Woodhouse
- Re: RE : Is JFFS2 thread-safe?
  - From: David Woodhouse
- Re: RE : Is JFFS2 thread-safe?
  - From: Gary Thomas

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]