PIXIL development - now?

[Troy Davis]

According to the libpthread library readme it uses clone(), not vfork().

from the readme
"LinuxThreads provides kernel-level threads: each thread is a separate
Unix process, sharing its address space with the other threads through
the new system call clone(). Scheduling between threads is handled by
the kernel scheduler, just like scheduling between Unix processes."

Not sure if this will benefits us though.

On a side note, I have got pixil's viewml compiled/linked, but haven't been able
to test it on hardware. If someone want to test it, i've put it up on my site
http://gpf.dcemu.co.uk/viewml.gz ,just extract it to /usr/pixil/bin

Thanks,
Troy(GPF)

Quoting Amadeus <amadeus at iksw-muees.de>:

> Hello Nanomad,
>
> On Samstag, 22. September 2007, Nanomad wrote:
> > Ok, got it running here too
> > Seems a bit sluggish, but it is working almost fine.
> > Maybe we could improve pixil in this way:
> > Converting fork() to vfork() is handy for testing purposes under
> > uClinux, but I think we should go on and convert those fork() into
> > pthreads calls (since libpthread is working, right?).
>
> Can you explain WHY we should do this?
>
> Pthreads are implemented as calls to vfork(), so you get nothing.
>
> regards
> Amadeus
> --
> We're back to the times when men were men
> and wrote their own device drivers.
>
> (Linus Torvalds)
> --
> dslinux-devel mailing list
> dslinux-devel at dslinux.in-berlin.de
> http://mailman.dslinux.in-berlin.de/mailman/listinfo/dslinux-devel
>