linux-kernel - Re: [Bug #12208] uml is very slow on 2.6.28 host

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Dec 2008 01:49:41 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	rjw@...k.pl
CC:	a.p.zijlstra@...llo.nl, efault@....de, mingo@...e.hu,
	linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org,
	miklos@...redi.hu
Subject: Re: [Bug #12208] uml is very slow on 2.6.28 host

On Sat, 13 Dec 2008, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12208
> Subject		: uml is very slow on 2.6.28 host
> Submitter	: Miklos Szeredi <miklos@...redi.hu>
> Date		: 2008-12-12 9:35 (2 days old)
> References	: http://marc.info/?l=linux-kernel&m=122907463518593&w=4

I did a bisection, and this is the commit which is responsible:

  commit 464b75273f64be7c81fee975bd6ca9593df3427b
  Author: Peter Zijlstra <a.p.zijlstra@...llo.nl>
  Date:   Fri Oct 24 11:06:15 2008 +0200
  
      sched: re-instate vruntime based wakeup preemption
  
      The advantage is that vruntime based wakeup preemption has a better
      conceptual model. Here wakeup_gran = 0 means: preempt when 'fair'.
      Therefore wakeup_gran is the granularity of unfairness we allow in order
      to make progress.
  
      Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
      Acked-by: Mike Galbraith <efault@....de>
      Signed-off-by: Ingo Molnar <mingo@...e.hu>

Miklos
--
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/