This is the mail archive of the ecos-discuss@sourceware.org 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: One process with multiple threads??


graham_k wrote:
Sorry to be such a n00b, but can someone please explain WikiPedia's statement
that "eCos (embedded configurable operating system) is an open source,
royalty-free, real-time operating system intended for embedded systems and
applications which need only one process with multiple threads"?

Why only one process? And presumably the thread are what I would think of as
processes in "normal" terminology?
You can say. More common word is task.
I guess that what I am asking here is whether this is just a matter of
semantics (what's a process? what's a thread?) or if there are some
technical restrictions ...
Sometimes it is, depends on OS' documentation terminology, traditionally it all used to be processes.
Processes are supposed to be have their own address space and are usually isolated (by means of MMU). On the other hand, threads share common address space. Modern GP OSes such (Linux, etc) implement both - a process can consist of more threads.


With this respect, since all eCos tasks share common address space they are considered threads.

Thank you very much in advance for any clarification.



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


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