Sebastian.Sumpf at ...1...
Sat Aug 2 12:27:09 CEST 2014
On 07/29/2014 10:14 AM, Daniele Lacamera wrote:
> I've stomped onto an old post on this list, considering a port for picoTCP.
> If I understood correctly, the major concern was around the threading model.
> We now have a library that provides blocking socket operations in a
> OS-agnostic way:
> All you would need to provide is a couple of synchronization
> mechanisms (- a mutex and a msgqueue/semaphore) in your own -osal
> module, besides the clock source and the allocator as for any ports in
> the stack. Feel free to ask for any information, but please keep us in
> cc since we are not subscribed to the mailing list.
Thanks for the info, which sounds very interesting. Having not used
picoTCP, I do have two questions: How is the Gigabit-Ethernet
performance and does the stack support IPv6?
More information about the users