Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT




Loading

FreeRTOS+TCP and multi-'threading'

Posted by gwesp on November 8, 2017

Hi,

can anybody confirm that FreeRTOSsend() and FreeRTOSrecv() can be used concurrently (i.e., from different tasks) on the same socket? This is possible with the BSD interface, I'm just double-checking that the same semantics apply here.

Thanks and kind regards --Gerhard


FreeRTOS+TCP and multi-'threading'

Posted by heinbali01 on November 8, 2017

Hi Gerhard, yes, the library has been made that way: one task may call send(), while the other task calls recv(). That is perfectly safe.

Just make sure that you synchronise the closure event among the tasks: once you get a negative result that is unequal to -pdFREERTOS_ERRNO_EAGAIN, the connection has become invalid and the socket must be closed by calling FreeRTOS_closesocket().

Once the socket is closed, the other task may not use it any more, or the penalty will be that the application will crash.

In an embedded application, when resources are scarce, it would be preferable to handle both send() and recv() from within the same task.

Or even better, handle a whole set of sockets from a single task.

We have given an example of doing so in the HTTP and FTP protocols, which you can find in FreeRTOS-Plus-TCP/protocols.

That driver has a main call FreeRTOS_TCPServerWork(), which will call FreeRTOS_select(). The function select(), as you know, waits for any event that happens on a collection of handles (sockets, in this case). This may be a read, a write or an error event.

Regards,


FreeRTOS+TCP and multi-'threading'

Posted by gwesp on November 9, 2017

Thanks Hein for the quick reply.

What is the estimated resource usage of a task to handle the receive loop? Data input is pretty rare in our application (basically, just parameter changes). If it's not more than a couple 100 bytes, we'll rather favor clarity.


FreeRTOS+TCP and multi-'threading'

Posted by heinbali01 on November 9, 2017

What is the estimated resource usage of a task to handle the receive loop?

The biggest 'cost' will be the extra stack usage. Beside that, there will be a bit of extra task switching.

In my post here above, I mentioned the possibility of using FreeRTOS_select().

There is a simple +TCP alternative: couple a semaphore to one or more sockets.

~~~ FreeRTOSsetsockopt( xSocket, 0, FREERTOSSOSETSEMAPHORE, ( void * ) &xServerSemaphore, sizeof( &xServerSemaphore ) ); ~~~

After this coupling, the TCP/IP driver will give to the semaphore at each moment of interest:

● After sending a packet ( and TX space becomes available ) ● When new data has been received ● When something happens to the connection ( gain, lost )

The main loop can simply block on the semaphore. When it wakes up, all sockets will be checked in a non-blocking way.

Regards,


FreeRTOS+TCP and multi-'threading'

Posted by gwesp on November 9, 2017

OK. I looked at the stack usage, it is ca. 1k in our case.

This is largely dwarfed by buffer sizes. Do you have suggestions to optimize those in a memory constrained environment?

I just reduced our value of ipconfigNUMNETWORKBUFFER_DESCRIPTORS from 20 to 10, that gains us ca. 15k and appears to work just fine. Any other suggestions? The TCP stack seems to allocate a lot (ca. 37k) on the heap. Not quite clear where that's coming from, and what could further be tuned.

We have currently:

ipconfigNETWORKMTU 586 ipconfigTCPMSS 64 configNUMRXDESCRIPTORS 6 configNUMTXDESCRIPTORS 4

Performance is not important for our application, but we are a bit memory constrained (LPC1837, total ca. 100k). It will eventually send a few hundred bytes / s over a single TCP connection and occasionally (every few minutes) receive a settings command (couple 100). CPU load is not an issue.


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

FreeRTOS kernel V10 is available for immediate download. Now MIT licensed.


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS