On Mon, Jan 21, 2013 at 12:56 PM, Sonny Karlsson <[email protected]> wrote:
> On Mon, Jan 21, 2013 at 08:06:10PM +0200, Lauri Kasanen wrote: > > On Mon, 21 Jan 2013 18:16:14 +0100 > > Sonny Karlsson <[email protected]> wrote: > > > > + # is set to 0 monkey will launch one processor per thread. > > > > This line says it the wrong way around. Launching processors ;) > > > That would have been a pretty awesome feature. ;] > Attached new version with a more realistic comment. > Thanks for noticia more realistic > > > - Lauri > > -- > Sonny Karlsson > > _______________________________________________ > Monkey mailing list > [email protected] > http://lists.monkey-project.com/listinfo/monkey > > Hey!, thanks for the patch, but we have a few things to consider: it does not matter in terms of scalability if we launch the same number of workers per processor if the task is not assigned to it. I mean, this is totally correct and make sense to enable SMP on-demand. For years i have been opposite to implement this in the core due to the project targets which is Embedded Linux. But things have changed a little in terms of processors on different devices so we can do something different without affect the core. So i propose the following: Create a SMP plugin which auto-magically spawn N workers as N online CPU cores exists. And each worker is assigned to a specific CPU, you can check more of this in sched_setaffinity(2). This plugin is build by default but must be enabled manually in conf/plugins.load. Then we can implement a smp.conf file to define more strict policies about how the workers are distributed among the CPU cores available. comments ? -- Eduardo Silva http://edsiper.linuxchile.cl http://www.monkey-project.com
_______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
