From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kyle@mcmartin.ca
Subject: Re: [GIT PULL] percpu for 2.6.31
Date: Fri, 19 Jun 2009 07:39:44 +0200 [thread overview]
Message-ID: <20090619053944.GB8162@elte.hu> (raw)
In-Reply-To: <4A3AEE42.4010300@kernel.org>
* Tejun Heo <tj@kernel.org> wrote:
> Hello, again.
>
> Tejun Heo wrote:
> > Oops, my apologies. I had them as floating series and apparently used
> > different base commit when applying them. I did grep run and full yes
> > build on the original quilt tree but didn't after quiltimport. Sorry.
>
> I digged through git changelogs to find out where it went wrong.
> I did use the same base commit when quiltimporting but when I
> updated the patches on top of mainline two days ago, I forgot to
> quilt add the file and the mce change got committed to the base
> tree instead of quilt patch. After pulling the latest master into
> the quilt branch yesterday, I updated the series for newcomers and
> everything worked fine (as the base tree change got merged by
> git). quiltimporting of course lost the base tree change and
> thinking the output gotta be identical I didn't test the final git
> tree.
>
> Anyways, I'm dropping the for-linus branch from percpu tree,
> fixing it up, adding patchsets scheduled for .32 release and will
> try to get it merged into #linux-next.
Please create a -git based bit for the x86 side (as i asked you
previously) - we can certainly get that upstream sooner after the
necessary amount of testing.
Condolences for trying to improve a dozen SMP architectures at once,
you've ended up with:
- being forced to rebase all the time. (This will happen in the
cycle to come too: just watch as the conflicts in linux-next
mount up with the architecture trees. Your tree will become
crappy quickly due to the combined noise.)
- the 10x patch logistics end up killing your overall quality, let
crap creep in and cause breakage even on x86.
You wasted 3 months of your life on that. Now you've learned not to
do that ever again - i've been there, done that, got the T-shirt.
Just stick your new stuff behind an ARCH_HAS flag, add it to the
architecture(s) you care about and forget about the rest - let the
remaining arch maintainers pick things up in their own pace. You'll
get 90% of the benefits to Linux with just 30% of the work.
( Many wont btw: we still dont have lockdep support in all
architectures - 3 years and counting. It's a highly useful purely
sw feature with zero hardware dependencies. Fortunately it's
well-modularized and the functionality is non-essential. Percpu
allocation is not so lucky as it's essential functionality. )
Ingo
next prev parent reply other threads:[~2009-06-19 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:07 Tejun Heo
2009-06-18 21:22 ` Linus Torvalds
2009-06-18 21:39 ` Andrew Morton
2009-06-18 22:43 ` Tejun Heo
2009-06-19 6:49 ` Ingo Molnar
2009-06-18 22:33 ` Tejun Heo
2009-06-18 22:45 ` Tejun Heo
2009-06-19 1:47 ` Tejun Heo
2009-06-19 5:39 ` Ingo Molnar [this message]
2009-06-19 19:39 ` Linus Torvalds
2009-06-19 21:08 ` 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=20090619053944.GB8162@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--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
all inboxes | Powered by JetHome®