Hi Sylvain. Thanks a ton for the clarifications !!
On Sat, Aug 22, 2015 at 10:42 PM, Sylvain Rochet <[email protected]> wrote: > Hi Ajay, > > On Sat, Aug 22, 2015 at 10:20:27PM +0530, Ajay Garg wrote: > > > > I am sorry, I am not sure what is meant by an OS here. > > OS = FreeRTOS, ChibiOS, … understand something which provide multiple > loops using lightweight threads. > > > > I presume if there were an OS, then the environment would "not" be > > bare-metal (since we would be depending on the functionalities being > > provided by the OS) ? > > In embedded context, bare metal = everything runs in the main loop, no > threads, no context switch, no task priorities. > > For lwIP, > > NO_SYS = 1 = bare metal, lwIP event handler is integrated within the main > loop. > > NO_SYS = 0 = threaded, lwIP event handler runs within its own thread. > Well, that's it ... In the application that we have designed and coded so far, everything has been kept single-threaded only (so as now to have any dependency on any third-party embedded-device-vendors). So, it turns out, that we "do" need to use NO_SYS = 1 But I get your point, it should be feasible to integrate the functionality with NO_SYS = 1 (though it might require some code-rearrangement in lwIP). Anyhow, if there are some examples of this particular scenario (NO_SYS = 1, everything within the main loop), kindly let know. It would save some time ticks for us :) Thanks again. Thanks and Regards, Ajay > > > On a Linux/win32 host, everything obviously runs inside a heavy process, > but the bare metal vs threaded still apply. > > > Sylvain > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users > -- Regards, Ajay
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
