Hello, The current status for week 1: - I setup the working and testing environment (I needed a two-core HT aware CPU [1]). - I setup a repo in github [2] and also I will make periodic updates to my repo on the leaf [3]. - I studied the sysctl interface through which I am going to modify the behaviour of the scheduler (it's more flexible this way then configs made at build time - thanks Alex for the tip). - I read a paper on SMT aware schedulers [4]
[1] http://leaf.dragonflybsd.org/~mihaic/hw/cpuinfo [2] https://github.com/mihaicarabas/dragonfly [3] http://gitweb.dragonflybsd.org/~mihaic/dragonfly.git [4] http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-619.pdf On Wed, Apr 25, 2012 at 11:03 AM, Mihai Carabas <mihai.cara...@gmail.com>wrote: > Hello everyone! > > > My name is Mihai Carabas and this summer I will be working on the > DragonFlyBSD scheduler. The goal of the project is to make the scheduler > aware of the underlaying hyperthreading CPUs, in order to make better > decisions. > > First of all, I will have to build up the testing infrastructure (a > physical machine with at least 2 physical cores, each of them having HT > enable). At this step I will develop a test suite that stress up the > scheduler and make different measurements. These measurements will be the > reference for comparing the results obtained after modifying the scheduler. > > In the next step, I have to develop a mechanism for grouping the CPUs in > domains (scheduling domains or in other words: CPUs that are on the same > physical core). > The actual implementation of the HT aware is described in a previous post > [1] on the list and in my application [2]. To sum up, here I will treat > different use cases (eg: "passive" scheduling - select a free physical > CPU (if available) for the next thread to schedule; "active" scheduling" > - if a physical CPU becomes idle and on another CPU are running two > threads, migrate one of them on the idle physical cpu; etc.). > > [1] http://leaf.dragonflybsd.org/mailarchive/kernel/2012-03/msg00066.html > [2] > http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/mihaicarabas/1 > >