All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Fr?d?ric Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] scheduler changes for v3.10
Date: Tue, 30 Apr 2013 18:23:00 +0200	[thread overview]
Message-ID: <20130430162300.GB28821@gmail.com> (raw)
In-Reply-To: <20130430153512.GA21930@redhat.com>


* Stanislaw Gruszka <sgruszka@redhat.com> wrote:

> 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@kernel.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.

Linus, would you like me to revert d9a3c9823a2e and re-send the pull 
request?

I intended to queue up Stanislaw's fixes in sched/urgent as the real 
solution, but they arrived earlier today and are too fresh.

Thanks,

	Ingo

  reply	other threads:[~2013-04-30 16:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30  6:58 [GIT PULL] scheduler changes for v3.10 Ingo Molnar
2013-04-30 14:49 ` Linus Torvalds
2013-04-30 15:35   ` Stanislaw Gruszka
2013-04-30 16:23     ` Ingo Molnar [this message]
2013-04-30 16:27       ` Linus Torvalds
2013-04-30 16:30         ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130430162300.GB28821@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.