From: Ingo Molnar <mingo@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus <torvalds@linux-foundation.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: linux-next: Tree for Nov 14
Date: Wed, 14 Nov 2012 08:39:29 +0100 [thread overview]
Message-ID: <20121114073929.GA3130@gmail.com> (raw)
In-Reply-To: <20121113225635.a848fd6c.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 14 Nov 2012 07:47:26 +0100 Ingo Molnar <mingo@kernel.org> wrote:
>
> >
> > * Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > > On Wed, 14 Nov 2012 16:30:42 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > > News: next-20121115 (i.e. tomorrow) will be the last release until
> > > > next-20121126 (which should be just be after -rc7, I guess - assuming
> > > > that Linus does not release v3.7 before then), so if you want something
> > > > in linux-next for a reasonable amount of testing, it should probably be
> > > > committed tomorrow.
> > >
> > > It would help if the old sched/numa code wasn't in -next while
> > > you're away. That would give me a clean run at 3.7 and will
> > > make it easier for others to integrate and test the four(!)
> > > different autoschednumacore implementations on top of
> > > linux-next.
> > >
> > > Pretty please?
> >
> > The next integration should have this solved: I have removed the
> > old sched/numa bits, replaced by the latest rebased/reworked
> > numa/core bits.
> >
>
> That solves one problem, but I still need to route around the
> numa stuff when preparing the 3.8-rc1 merge. Again!
I'm eyeing a v3.8 merge... modulo unforeseen problems. This has
been going on for way too long.
numa/core performs very well, and the rest can be done
iteratively.
The mm/ bits changed very little due to the latest rounds of
review. Most of the discussion centered around specific
implementational details and naming - and where we were wrong I
changed the code - numa/core sums up the consensus so far.
If I missed anything let me know and I'll fix the code ASAP ...
Thanks,
Ingo
next prev parent reply other threads:[~2012-11-14 7:39 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 5:30 linux-next: Tree for Nov 14 Stephen Rothwell
2012-11-14 5:37 ` Andrew Morton
2012-11-14 5:53 ` Andrew Morton
2012-11-14 6:47 ` Ingo Molnar
2012-11-14 6:56 ` Andrew Morton
2012-11-14 7:15 ` Stephen Rothwell
2012-11-14 7:24 ` Andrew Morton
2012-11-14 7:39 ` Ingo Molnar [this message]
2012-11-14 8:13 ` Hugh Dickins
2012-11-14 17:05 ` Rik van Riel
2012-11-15 12:10 ` Mel Gorman
2012-11-14 17:19 ` Linus Torvalds
2012-11-14 6:55 ` Stephen Rothwell
2012-11-14 7:03 ` Stephen Rothwell
2012-11-14 19:41 ` linux-next: Tree for Nov 14 (gpu/drm/i915) Randy Dunlap
2012-11-14 20:17 ` Andrew Morton
2012-11-15 0:59 ` [PATCH 1/2] asm-generic: add __WARN() to bug.h Randy Dunlap
2012-11-15 1:28 ` David Rientjes
2012-11-15 0:59 ` [PATCH 2/2] mm: balloon_compaction.c needs asm-generic/bug.h Randy Dunlap
2012-11-15 1:29 ` David Rientjes
2012-11-15 1:29 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 3:19 linux-next: Tree for Nov 14 Stephen Rothwell
2022-11-14 7:49 Stephen Rothwell
2019-11-14 8:31 Stephen Rothwell
2019-11-14 18:38 ` Naresh Kamboju
2019-11-14 20:11 ` Jan Stancek
2019-11-14 21:19 ` Arnd Bergmann
2018-11-14 5:26 Stephen Rothwell
2017-11-14 6:20 Stephen Rothwell
2016-11-14 7:23 Stephen Rothwell
2014-11-14 8:27 Stephen Rothwell
2014-11-15 21:19 ` Guenter Roeck
2014-11-16 2:33 ` Jiang Liu
2014-11-16 3:22 ` Guenter Roeck
2014-11-16 4:20 ` Jiang Liu
2014-11-16 6:56 ` Guenter Roeck
2014-11-16 8:24 ` Jiang Liu
2014-11-16 8:37 ` Jiang Liu
2014-11-16 15:42 ` Guenter Roeck
2014-11-16 16:01 ` Guenter Roeck
2014-11-16 16:11 ` Guenter Roeck
2014-11-17 5:12 ` Jiang Liu
2014-11-17 17:02 ` Guenter Roeck
2013-11-14 4:22 Stephen Rothwell
2011-11-14 3:43 Stephen Rothwell
2019-11-14 16:43 ` Christian Brauner
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=20121114073929.GA3130@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).