|
From: Frank V. C. <fr...@co...> - 2000-01-26 17:57:11
|
"Frank V. Castellucci" wrote: > > Jacob, > > Could you clarify one-to-one, one-to-many, and many-to-many? > > Thanks > -- "before he read the LinuxThreads article." I think we have two options: One-to-One : Uses the Linux "clone" api which is more efficient than fork. I perceived that clone, even though it calls it a process in the 'ps' display, is still running in the address space of the parent and they share the memory space. Thread n modifies something and it is visible to the other threads or main process thread. Many-to-Many : Combo of "clone" and a homegrown scheduler that takes its que from the kernel. I believe the latter to be an expensive (time, resources, acceptance) proposition but attractive none the less. If we think foward to the frameworks endeavor, it is reasonable to construct a Thread or Process framework that can be used to serve up default libcorelinux++ Thread (one-to-one) or whatever the framework extension desires (many to many, etc.). -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |