public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Marco Faella <mfaella@soe.ucsc.edu>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: looking for mutex usage
Date: Sat, 20 Nov 2004 09:39:00 -0000	[thread overview]
Message-ID: <20041120093859.GA8676@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <419EA216.4020505@cse.ucsc.edu>

On Fri, Nov 19, 2004 at 05:47:02PM -0800, Marco Faella wrote:
> Dear maintainers,
> 
> I'm a researcher in computer science at the
> University of California, Santa Cruz.
> 
> In my research group, we are developing a tool
> that analyzes the synchronization
> skeleton of multi-threaded programs.
> 
> We are focusing on eCos as our testbed, but
> we haven't been able to find an interesting
> test case so far.
> 
> Can you suggest any open source eCos application
> that makes non-trivial use of synchronization primitives
> like semaphores and mutexes?

eCos is intended for deeply embeeded applications. Such applications
tend to use specialised hardware and so does not naturally lend itself
to open source applications. I cannot think of a single instance of
somebody making there application available via an open source
license.

To be honest you might be better changes OS. Take a look at
Linux. There are probably enought non-trivial uses of spinlocks and
semaphores inside the kernel that you don't even need a particularly
interesting application. Look at one of the filesystems that uses
kernel threads, eg nfsd or kjournald. With 2.6 and kernel preemption
this gets even more interesting.

     Andrew

      reply	other threads:[~2004-11-20  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-20  1:47 Marco Faella
2004-11-20  9:39 ` Andrew Lunn [this message]

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=20041120093859.GA8676@biferten.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=mfaella@soe.ucsc.edu \
    /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).