Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965226Ab2B2Xdk (ORCPT ); Wed, 29 Feb 2012 18:33:40 -0500 Received: from mail-yx0-f174.google.com ([209.85.213.174]:40416 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932300Ab2B2Xdh (ORCPT ); Wed, 29 Feb 2012 18:33:37 -0500 Authentication-Results: mr.google.com; spf=pass (google.com: domain of yhlu.kernel@gmail.com designates 10.236.155.6 as permitted sender) smtp.mail=yhlu.kernel@gmail.com; dkim=pass header.i=yhlu.kernel@gmail.com MIME-Version: 1.0 In-Reply-To: References: <1330556858-11768-1-git-send-email-yinghai@kernel.org> <1330556858-11768-3-git-send-email-yinghai@kernel.org> Date: Wed, 29 Feb 2012 15:33:36 -0800 X-Google-Sender-Auth: pQbrDZ8xUtfbgkSiFDlGJWqU4sE Message-ID: Subject: Re: [PATCH 02/39] x86, PCI: have own version for pcibios_bus_to_resource From: Yinghai Lu To: Bjorn Helgaas Cc: Jesse Barnes , Benjamin Herrenschmidt , Tony Luck , David Miller , x86 , Dominik Brodowski , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 854 Lines: 23 On Wed, Feb 29, 2012 at 3:20 PM, Bjorn Helgaas wrote: > On Wed, Feb 29, 2012 at 4:07 PM, Yinghai Lu wrote: >> x86 does not need to offset the address. So we can skip that costing offset >> searching. > > I tried to start a discussion about this patch (and others), but I > don't think you responded: > http://marc.info/?l=linux-pci&m=133036414506921&w=2 this patch does reduce some not needed ops. and it does not affects your effects, and it just make x86 not get punished. let's let Jesse and x86 maintainers to decide if this patch is needed. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/