Dear Manjunath, I do agree on the mentioned points in your mail.
As I understood tasks are non-preemptive and are run-to completion. Invocation of task ( aka command) and completion of task (aka event) constitutes split-phase operation. It is not that you can preempt a running task and run another task. Coming to memory allocation, you are agreeing on lack of it in TinyOS. Coming to memory management/VM, I never said you can't implement in TinyOS. I had only pointed out that this facility is not there in TinyOS. Please point me to some paper/application of TinyOS which discusses about running multiple applications on the core TinyOS without using any other library. Regards Adi On Wed, Jan 6, 2010 at 3:50 PM, Manjunath Doddavenkatappa < [email protected]> wrote: > > Dear Adi, > > Following is my perception. > > Process mangement: > > WSNs are event-driven thus demanding CPU to be switched among the > tasks corresponding to events (interrupts). Therefore, the decision not > include usual process management. However, TinysOS/nesC does have > split-phase operations to avoid a task monopolizing CPU. > > Dynamic memory allocation: > > TinyOS have several implementations of supporting dynamic memeory > allocation starting from TinyAlloc (I remember using it way back in 2005). > Please have a look at the mail here it gives extremely useful insights: > (last part of the mail answered by Prof. Phil Levis) > > http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-October/012856.html > > Virtual memeory: > > Nothing stops one to add a TinyOS componet supporting virtual memory > provided motes have MMU. This is not the limitation of TinyOS. Motes usually > do not posses MMU as it consumes power in mappping each instruction and it > also adds to the cost of the mote. > > Multiple applications: > > Multiple functionalities can co-exist in a single TinyOS image. > > Regards, > Manjunath D > > > ################################################################################################################ > > *************************************************************************************************************** > > > On Wed, 6 Jan 2010, [email protected] wrote: > > Hi Aslam, >> >> Please enlighten me on the following things with regards to TinyOS >> >> * Does TinyOS supports Process maangement? >> * Can I load multiple applications/programs on TinyOS (without any other >> supporting software)? >> * Do we have a dynamic memory allocation or memory management mechanism in >> TinyOS? >> >> Regards >> Adi >> >> >> On 06-Jan-2010 5:07am, Faisal Aslam <[email protected]> >> wrote: >> >>> Hi, >>> >> >> >> I disagree ... >>> >> >> >> >> >> >> TinyOS is a tiny Operating System. It has a scheduler and it manage >>> memory >>> >> >> >> (resources). These are characteristics of OS. >>> >> >> >> The modules, configurations are NOT available due to TinyOS but they are >>> >> >> >> available due to NesC. Someone can write code in NesC without using >>> >> >> >> TinyOS. >>> >> >> >> >> >> >> best regards, >>> >> >> >> Faisal >>> >> >> >> >> >> >> Hi Adi, >>>> >>> >> >> Thank you very much. >>>> >>> >> >> Can I ask you something else? Can we say that modules/configurations are >>>> >>> >> >> components? >>>> >>> >> >> >>>> >> >> Thanks >>>> >>> >> >> >>>> >> >> 2010/1/5 Adi Mallikarjuna Reddy V [email protected]> >>>> >>> >> >> >>>> >> >> TinyOS is not really an operating system and it is not a middleware >>>>> >>>> >> >> also. TinyOS uses component model at compile time and single static >>>>> >>>> >> >> image at >>>>> >>>> >> >> run time. TinyOS allows applications to be constructed from a large >>>>> >>>> >> >> number of very fine-grained components (modules and configurations). >>>>> >>>> >> >> >>>>> >> >> Mate can be considered as a middleware on top of TinyOS. >>>>> >>>> >> >> >>>>> >> >> Regards >>>>> >>>> >> >> Adi >>>>> >>>> >> >> >>>>> >> >> >>>>> >> >> On Tue, Jan 5, 2010 at 6:23 PM, Alfred NOBEL >>>>> >>>> >> >> [email protected]>wrote: >>>>> >>>> >> >> >>>>> >> >> Hi All, >>>>>> >>>>> >> >> Please, can we consider TinyOS operating system as a middleware? if yes >>>>>> >>>>> >> >> how is that? >>>>>> >>>>> >> >> Thank you so much. >>>>>> >>>>> >> >> >>>>>> >> >> -- >>>>>> >>>>> >> >> Best regards, >>>>>> >>>>> >> >> Alfred.Nooobel >>>>>> >>>>> >> >> >>>>>> >> >> _______________________________________________ >>>>>> >>>>> >> >> Tinyos-help mailing list >>>>>> >>>>> >> >> [email protected] >>>>>> >>>>> >> >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>>>>> >>>>> >> >> >>>>>> >> >> >>>>> >> >> >>>>> >> >> >>>> >> >> >>>> >> >> -- >>>> >>> >> >> Best regards, >>>> >>> >> >> Alfred.Nooobel >>>> >>> >> >> _______________________________________________ >>>> >>> >> >> Tinyos-help mailing list >>>> >>> >> >> [email protected] >>>> >>> >> >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>>> >>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >>> >> >> >> Tinyos-help mailing list >>> >> >> >> [email protected] >>> >> >> >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>> >> >> >> >>
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
