public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: mctim <mctim@polyu.edu.hk>
Cc: "ecos-maintainers@sources.redhat.com"
	<ecos-maintainers@sources.redhat.com>
Subject: Re: multi-threading in eCos and Linux
Date: Mon, 04 Nov 2002 07:04:00 -0000	[thread overview]
Message-ID: <3DC68C52.1030507@eCosCentric.com> (raw)
In-Reply-To: <3DDCC4D1@webmail.polyu.edu.hk>

mctim wrote:
> Hi,
> 
> I am going to write a cross-platform multithreading program in eCos and Linux, 
> as I know, both eCos and Linux are support POSIX thread (p_thread) and eCos 
> also have some API  (cyg_thread) to handle multi-threading. I want to write an 
> crossplatform compatible program which suit to eCos and Linux. So I want to 
> use POSIX thread to develop this program. But I afraid the performance of 
> POSIX thread in eCos is not good as cyg_thread in eCos. Could you suggest me 
> that which threading API in eCos is prefered( p_thread or cyg_thread)? Thanks 
> a lot.

This isn't really appropriate to the maintainers list but I'll reply anyway.

While it's true that the native cyg_threads stuff is the most efficient, 
you'll find that eCos is a sufficiently lightweight operating system 
anyway that the very small overhead of using POSIX threads will not have 
any real impact. If your requirements are that it is cross platform, then 
POSIX threads are definitely the way to go.

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

      reply	other threads:[~2002-11-04 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-03 23:10 mctim
2002-11-04  7:04 ` Jonathan Larmour [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=3DC68C52.1030507@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=mctim@polyu.edu.hk \
    /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).