This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Net BSD network stack posix tasks -
- From: Robin Randhawa <robin dot randhawa at gmail dot com>
- To: Alok Singh <aloks at broadcom dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 29 May 2007 18:20:42 +0100
- Subject: Re: [ECOS] Net BSD network stack posix tasks -
- References: <FE7FB54DCB7C6949A1D3F9FF22DA6C135AAF0E@lvl7in-mail01.lvl7.com>
Greetings.
Your description is quite puzzling.
POSIX threads in eCos have nothing to do with the network stack, not
directly at least. The POSIX functionality is essentially a carefully
crafted set of wrappers over the basic eCos threading architecture.
Think of the networking stack as a state machine implementation borrowed
from a BSD derivative and driven using native eCos threads running under
the eCos kernel.
Now you can take a POSIX application and via the POSIX "wrapper" link
the application to the networking stack and the kernel.
My humble and pointed suggestion : RTFM.
eCos has abundant documentation that sheds light on these concepts.
Cheerio!
Robin
On Tue, 2007-05-29 at 22:35 +0530, Alok Singh wrote:
> Hi,
> I don't understand licensing issues much. I've a question. Am I allowed
> to convert network stack threads to posix threads instead of native cyg
> threads? I've compatibility issues making ecos network stack work with
> my application (Posix based.) Though there are ways to overcome this
> issue, but they affect the performance of the system.
>
>
> regards,
> Alok
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss