|
From: Frank V. C. <fr...@co...> - 2001-03-17 01:17:33
|
Whew, long week. How are we, where we are, are we? -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Hans D. <dul...@eg...> - 2001-03-17 03:40:46
|
"Frank V. Castellucci" wrote: > > Whew, long week. How are we, where we are, are we? > Here I am... adding lines to the Thread and ThreadContext implementation. One question come to mind? Why there is no 'pthread_*' call at all in Thread and ThreadContext? Not even pthread_create? From 24 requirements item in req1588.html, I discovered that 12 of them have been implemented. I added 2 more implemented requirements: created and blocked count. Next I'll tackle the priority related. But.... should I use pthread_*? > -- > Frank V. Castellucci > http://corelinux.sourceforge.net > OOA/OOD/C++ Standards and Guidelines for Linux > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/lists/listinfo/corelinux-develop -- Hans Dulimarta, Ph.D. | dul...@co... Research Associate | http://www.egr.msu.edu/~dulimart P: 517-432-7589 | http://corelinux.sourceforge.net F: 760-281-7691 http://freshmeat.net/projects/snapsource Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824 |
|
From: Frank V. C. <fr...@co...> - 2001-03-17 11:21:01
|
Hans Dulimarta wrote: > > "Frank V. Castellucci" wrote: > > > > Whew, long week. How are we, where we are, are we? > > > > Here I am... adding lines to the Thread and ThreadContext > implementation. > > One question come to mind? Why there is no 'pthread_*' call > at all in Thread and ThreadContext? Not even pthread_create? pthread is a user space thread mechanism. If you are running on a SMP machine, the threads that are created using pthread do not take advantage of the other processors. Lets stick to "clone". > >From 24 requirements item in req1588.html, I discovered that > 12 of them have been implemented. Cool. Are you finding it interesting, or is it boring stuff? > I added 2 more implemented requirements: created and blocked > count. > > Next I'll tackle the priority related. But.... should I use > pthread_*? By the way, if you are going to add priority you may consider the actual Linux call to be wrapped in a static in Environment? > > > -- > > Frank V. Castellucci > > http://corelinux.sourceforge.net > > OOA/OOD/C++ Standards and Guidelines for Linux > > > > _______________________________________________ > > Corelinux-develop mailing list > > Cor...@li... > > http://lists.sourceforge.net/lists/listinfo/corelinux-develop > > -- > Hans Dulimarta, Ph.D. | dul...@co... > Research Associate | > http://www.egr.msu.edu/~dulimart > P: 517-432-7589 | http://corelinux.sourceforge.net > F: 760-281-7691 http://freshmeat.net/projects/snapsource > Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824 > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/lists/listinfo/corelinux-develop -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Hans D. <dul...@eg...> - 2001-03-17 22:46:20
|
"Frank V. Castellucci" wrote: > > pthread is a user space thread mechanism. If you are running on a SMP > machine, the threads that are created using pthread do not take > advantage of the other processors. > > Lets stick to "clone". > OK. > > Cool. Are you finding it interesting, or is it boring stuff? > Well, I guess it is in between.....the repetitious part is kind of boring. The new part, such as trying to understand the logic of the existing code, is challenging. > By the way, if you are going to add priority you may consider the actual > Linux call to be wrapped in a static in Environment? I also found getpid(), getppid(), and clone() call in Thread.cpp. Maybe we should move them to Environment? Is the Enviroment designed to be a "leaf" module as a wrapper of all the underlying system? If yes, we should not put a call to Thread::getKernelError() in Environment::setupCommonAccess. > > > > > > -- > > > Frank V. Castellucci > > > http://corelinux.sourceforge.net > > > OOA/OOD/C++ Standards and Guidelines for Linux > > > > > > _______________________________________________ > > > Corelinux-develop mailing list > > > Cor...@li... > > > http://lists.sourceforge.net/lists/listinfo/corelinux-develop > > > > -- > > Hans Dulimarta, Ph.D. | dul...@co... > > Research Associate | > > http://www.egr.msu.edu/~dulimart > > P: 517-432-7589 | http://corelinux.sourceforge.net > > F: 760-281-7691 http://freshmeat.net/projects/snapsource > > Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824 > > > > _______________________________________________ > > Corelinux-develop mailing list > > Cor...@li... > > http://lists.sourceforge.net/lists/listinfo/corelinux-develop > > -- > Frank V. Castellucci > http://corelinux.sourceforge.net > OOA/OOD/C++ Standards and Guidelines for Linux > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/lists/listinfo/corelinux-develop -- Hans Dulimarta, Ph.D. | dul...@co... Research Associate | http://www.egr.msu.edu/~dulimart P: 517-432-7589 | http://corelinux.sourceforge.net F: 760-281-7691 http://freshmeat.net/projects/snapsource Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824 |
|
From: Frank V. C. <fr...@co...> - 2001-03-17 23:03:41
|
Hans Dulimarta wrote: > > > By the way, if you are going to add priority you may consider the actual > > Linux call to be wrapped in a static in Environment? > > I also found getpid(), getppid(), and clone() call in > Thread.cpp. > Maybe we should move them to Environment? See below :) > > Is the Enviroment designed to be a "leaf" module as a > wrapper of > all the underlying system? If yes, we should not put a call > to Thread::getKernelError() in > Environment::setupCommonAccess. Your right, organize a new static class if you like which covers the behavior you want, we can also use namespaces to localize the context: corelinux::Enviornment corelinux::Enviornment::Process etc. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |