From: David Woodhouse <dwmw2@infradead.org>
To: Vincent Catros <Vincent.Catros@elios-informatique.fr>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RE : [ECOS] Is JFFS2 thread-safe?
Date: Fri, 28 Nov 2003 16:09:00 -0000 [thread overview]
Message-ID: <1070035746.13188.17.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <1070018876.10048.35.camel@hades.cambridge.redhat.com>
On Fri, 2003-11-28 at 11:27 +0000, David Woodhouse wrote:
> +#ifdef CYGPKG_KERNEL
> +#include <cyg/kernel/kapi.h>
> +#define spin_lock(lock) cyg_scheduler_lock()
> +#define spin_unlock(lock) cyg_scheduler_unlock()
> +#define spin_lock_bh(lock) cyg_scheduler_lock()
> +#define spin_unlock_bh(lock) cyg_scheduler_unlock()
Hmmm. I forgot eCos now had SMP support, and has its own spinlocks.
Can't say I much like the idea of putting in a #define to call a C
function which is a wrapper around a C++ class which in turn is a
wrapper round the original HAL functions... or in fact in the common
case is just a dummy counter which doesn't actually lock the scheduler
to avoid preemption... is that intentional?
--
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
next prev parent reply other threads:[~2003-11-28 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 9:15 Vincent Catros
2003-11-27 0:27 ` David Woodhouse
2003-11-27 9:12 ` [ECOS] RE : " Vincent Catros
2003-11-27 9:36 ` [ECOS] " David Woodhouse
2003-11-27 10:00 ` [ECOS] RE : " Vincent Catros
2003-11-27 10:24 ` [ECOS] " David Woodhouse
2003-11-28 11:14 ` [ECOS] " David Woodhouse
[not found] ` <1070018876.10048.35.camel@hades.cambridge.redhat.com>
2003-11-28 16:09 ` David Woodhouse [this message]
2003-11-29 14:54 ` Gary Thomas
2003-11-29 15:46 ` David Woodhouse
2003-11-29 15:47 ` Nick Garnett
2003-11-29 19:40 ` David Woodhouse
2003-11-27 17:02 ` Vincent Catros
2003-11-28 11:09 ` [ECOS] " David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1070035746.13188.17.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=Vincent.Catros@elios-informatique.fr \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).