Message-ID: <47C5E977.2010401@jp.fujitsu.com>
Date: Wed, 27 Feb 2008 17:51:35 -0500
From: Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071031)
MIME-Version: 1.0
To: mingo@elte.hu
CC: Kei Tokunaga <tokunaga.keiich@jp.fujitsu.com>,
       linux-kernel@vger.kernel.org
Subject: A strange behavior of sched_fair
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2119
Lines: 52

Hi Ingo,

I am playing around with sched_fair and cgroup, and it seems like
I hit a possible bug.  Could you also check if that is a bug?

Description of behavior:
   Start a cpu-bound task (t1), attach it to a cgroup (cgA), and let the
   task to run for a while (e.g. several tens of seconds or a couple of
   minutes would be adequate.)  Then, start another cpu-bound task (t2)
   and attach it to cgA in the way described in "Steps to Reproduce" section.
   You will see t1 does not get run for a while.
   (The tasks may not have to be cpu-bound, but it is easier to see the
    behavior using cpu-bound tasks.)

How reproducible:
   Always.

Environments where I saw the behavior:
   2.6.25-rc3 with resource management functions enabled on ia64 box.

Steps to Reproduce:
   # mkdir /dev/cgroup
   # mount -t cgroup -ocpuset,cpu cpu /dev/cgroup
   # mkdir /dev/cgroup/{a,b}
   # echo 0 > /dev/cgroup/a/cpuset.cpus
   # echo 0 > /dev/cgroup/b/cpuset.cpus
   # echo 1 > /dev/cgroup/a/cpuset.mems
   # echo 1 > /dev/cgroup/b/cpuset.mems
   # echo $$ > /dev/cgroup/b/tasks
   # ./a.out & echo $! > /dev/cgroup/a/tasks (a.out is just a for-loop program)
     [Wait for several tens of seconds or a couple of minutes.]
   # ./a.out2 & echo $! > /dev/cgroup/a/tasks (a.out2 is just a for-loop program)
     [You will see a.out does not get run for a while by running top command.]

Additional Info:
   a.out2 needs to be started from the shell of cgroup-b in order to
   reproduce the problem (, unless the system is UP.)  Starting a.out2
   in the manner, se->vruntime (or something to create the se->vruntime)
   of a.out2 seems to be initialized to a small value, compared to the
   value of a.out.  And the fair scheduler only runs a.out2 until the
   se->vruntime catches up with the se->vruntime of a.out.

Thanks,
Kei
--
Kei Tokunaga
Fujitsu (Red Hat On-site Partner)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/