From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
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:30:32 +0200 [thread overview]
Message-ID: <20130430163032.GA3999@gmail.com> (raw)
In-Reply-To: <CA+55aFwsv+p3wqx5eMr3iNPxmPZhSx-h5s5R7s9yd314Muajvg@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Tue, Apr 30, 2013 at 9:23 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Linus, would you like me to revert d9a3c9823a2e and re-send the pull
> > request?
>
> I took the pull request, but I'd like to see the non-64-bit divide
> version before the merge window ends. [...]
Yeah, wanted to apply it later today or tomorrow, and push it to you this
week - well before the end of the merge window.
> [...] And with no more div_rem users I think we should at least
> double-check that the new div64_u64() (that uses the new div64_u64_rem)
> isn't noticeably slower than the old one. If it is, we should revert
> that new (and then unused) div64 code too.
Correct, this is what Stanislaw's series from earlier today does:
[PATCH -tip 1/4] sched: Avoid cputime scaling overflow
[PATCH -tip 2/4] sched: Do not account bogus utime
[PATCH -tip 3/4] sched: Avoid prev->stime underflow
[PATCH -tip 4/4] Revert "math64: New div64_u64_rem helper"
so it gets rid of the div64_u64_rem() bits as well.
Thanks,
Ingo
prev parent reply other threads:[~2013-04-30 16:30 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
2013-04-30 16:27 ` Linus Torvalds
2013-04-30 16:30 ` Ingo Molnar [this message]
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=20130430163032.GA3999@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.