thank you for the answer. next question (out of curiosity, sorry if it is overstretching the OP) is in architecture without any MMU, what does syscall like fork() get translate into? the fact that fork() does not exists on non-MMU is discussed everywhere, but then how is it replaced? For example, the following seemed to imply fork() inside application should continue to compile (but should not give error when run, right?): http://mailman.uclinux.org/pipermail/uclinux-dev/2003-September/020871.html http://mailman.uclinux.org/pipermail/uclinux-dev/2003-September/021010.html is it just a passthrough? And does "Task-struct" even exists in non-MMU architecture? On Tue, Oct 7, 2008 at 4:31 PM, Rene Herman <rene.herman@xxxxxxxxxxxx> wrote: > On 07-10-08 10:15, Peter Teoh wrote: > >> In general, I am just trying to understand what are the entities that >> can be schedule on the runqueue. > > Threads (ie, things with a task_struct). So yes -- if you specifically > create a thread, such as with kthread_run(), that thread is scheduled. (and > it's irrelevant if the thread has or hasn't a userspace in that respect). > > Rene. > -- Regards, Peter Teoh -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
