linux-kernel - Re: [GIT PULL] scheduler changes for v3.10

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, 30 Apr 2013 17:35:20 +0200
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] scheduler changes for v3.10

On Tue, Apr 30, 2013 at 07:49:43AM -0700, Linus Torvalds wrote:
> On Mon, Apr 29, 2013 at 11:58 PM, Ingo Molnar <mingo@...nel.org> wrote:
> >
> > Please pull the latest sched-core-for-linus git tree from:
> >
> > The main changes in this development cycle were:
> >
> >   - full dynticks preparatory work by Frederic Weisbecker
> 
> Why does this have the crappy cputime scaling overflow code, when we
> had a long thread about how to do it right *without* any 64-bit
> divides, including a quality-tested patch?
> 
> This still has the garbage "div64_u64_rem()" crap which actually SLOWS
> DOWN 32-bit code even when not used (becuse it makes "div64_u64()"
> calculate it even when unnecessary.
> 
> WTF happened here? I and others spent efforts so that we wouldn't need
> this kind of crap.

I'm sorry, I was on vacations and has some other work to do, so I didn't
send patches in timely manner. I just posted them today.

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