[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20090129153709.f368625e.akpm@linux-foundation.org>
Date: Thu, 29 Jan 2009 15:37:09 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Mike Galbraith <efault@....de>,
Gregory Haskins <ghaskins@...ell.com>
Cc: linux-kernel@...r.kernel.org
Subject: sched behaviour (was: Re: linux-next: Tree for January 26)
On Mon, 26 Jan 2009 19:23:49 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
The machine is 8-way x86_64. In one window it is running `make -j32
vmlinux'.
In another window I run the `fpatch' command. fpatch is a scruffy
shell script from
http://userweb.kernel.org/~akpm/stuff/patch-scripts.tar.gz which does a
few mv's, cp's, etc.
current mainline:
akpm2:/usr/src/25> time fpatch b kernel/sched.c
fpatch b kernel/sched.c 0.02s user 0.09s system 33% cpu 0.338 total
Jan 26 linux-next:
akpm2:/usr/src/25> time fpatch b kernel/sched.c
fpatch b kernel/sched.c 0.02s user 0.05s system 0% cpu 32.739 total
Machine basically unusable, user unhappy!
I'm assuming it's a scheduler problem - everything is in pagecache.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists