mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: astarikovskiy@suse.de, len.brown@intel.com,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: mpparse merge
Date: Thu, 10 Apr 2008 12:14:11 +0200	[thread overview]
Message-ID: <20080410101408.GA12853@elte.hu> (raw)
In-Reply-To: <20080410092947.GA32376@basil.nowhere.org>


(Cc:-ing lkml because obviously others are interested in this topic too)

* Andi Kleen <andi@firstfloor.org> wrote:

> Refering to 
> 
> commit 9d92083afb7cabe86c166dce9cc569eabbbd6f99
> Author: Alexey Starikovskiy <astarikovskiy@suse.de>
> Date:   Fri Apr 4 23:43:18 2008 +0400
> 
>     x86: merge mpparse_{32,64}.c
> 
> in linux-next.
> 
> About half of the ifdefs seem to be because 32bit does irq compression 
> and 64bit does not. Len removed that at some point, but when the files 
> are merged I would rather just readd 64bit irq compression (or move 
> 64bit over to per cpu vectors) than have this ifdef jungle

the way Alexey did it is the safest way of doing unifications: keep it 
simple and finegrained first, keep the more complex steps to later. We 
try to stick to that even if there's a temporary jungle of #ifdefs. In a 
related discussion (which was unfortunately private too so no URLs) you 
suggested to Alexey to redesign the mp-parsing code first, then unify 
it. That's the worst possible approach to unification and i advise 
everyone against doing it that way. I very much agree with unifying irq 
vector management - it's not a simple task at all.

	Ingo

       reply	other threads:[~2008-04-10 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080410092947.GA32376@basil.nowhere.org>
2008-04-10 10:14 ` Ingo Molnar [this message]
2008-04-10 10:42   ` Andi Kleen

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=20080410101408.GA12853@elte.hu \
    --to=mingo@elte.hu \
    --cc=andi@firstfloor.org \
    --cc=astarikovskiy@suse.de \
    --cc=hpa@zytor.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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®