linux-kernel - Re: Please, put 64-bit counter per task and incr.by.one each ctxt switch.

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]

Message-Id: <1203875611.4508.2.camel@homer.simson.net>
Date:	Sun, 24 Feb 2008 18:53:31 +0100
From:	Mike Galbraith <efault@....de>
To:	"J.C. Pizarro" <jcpiza@...il.com>
Cc:	Rik van Riel <riel@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Please, put 64-bit counter per task and incr.by.one each ctxt
	switch.


On Sun, 2008-02-24 at 14:12 +0100, J.C. Pizarro wrote:

> On 2008/2/24, Mike Galbraith <efault@....de> wrote:
> >  > One reason: for the objective of gain interactivity, it's an issue that
> >  >  CFS fair scheduler lacks it.
> >
> > A bug report would be a much better first step toward resolution of any
> >  interactivity issues you're seeing than posts which do nothing but
> >  suggest that there may be a problem.
> >
> >  First define the problem, _then_ fix it.
> 
> It's blind eternal problem in overloaded CPU scenario in the desktops.

Define the problem.. please?  I won't repeat myself again.

	-Mike

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