All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Rajesh Shah <rajesh.shah@intel.com>, Andi Kleen <ak@suse.de>,
	len.brown@intel.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz,
	acpi-devel@lists.sourceforge.net, gregkh@suse.de
Subject: Re: [patch 2/2] x86_64: Collect host bridge resources
Date: Tue, 24 May 2005 10:37:25 -0700	[thread overview]
Message-ID: <20050524103724.A22049@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050524205855.A8367@jurassic.park.msu.ru>; from ink@jurassic.park.msu.ru on Tue, May 24, 2005 at 08:58:55PM +0400

On Tue, May 24, 2005 at 08:58:55PM +0400, Ivan Kokshaysky wrote:
> On Tue, May 24, 2005 at 08:45:36AM -0700, Rajesh Shah wrote:
> > The concern here isn't just increasing the size of pci_bus. The
> > resource pointers in pci_bus point to resource structures in the
> > corresponding pci_dev structure for p2p bridges. If we want to
> > maintain this scheme, we'd have to increase the number of resources
> > in the pci_dev structure too, which increases it for every single
> > pci device in the system.
> 
> No. The pci_bus resource pointers are just pointers to _some_ resources
> and generally aren't tied to particular pci device. For example, the
> root pci buses often don't even have corresponding bus->self structure,
> and bus resources are pointers to global io[mem,port]_resource.

For the transparent p2p bridge problem you mentioned, wouldn't you
be dealing with p2p bridges, and therefore expect the pci_bus
resource pointers to point to the corresponding pci_dev resources?
Or are you proposing to decouple pci_bus resource pointers from 
pci_dev completely? From quick code inspection, that seems to be
not too much trouble to increase from 4 then.

Rajesh

  reply	other threads:[~2005-05-24 17:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21  0:42 [patch 0/2] Collecting host bridge resources rajesh.shah-ral2JQCrhuEAvxtiuMwx3w
2005-05-21  0:42 ` rajesh.shah
2005-05-21  0:42 ` [patch 1/2] i386: collect " rajesh.shah-ral2JQCrhuEAvxtiuMwx3w
2005-05-21  0:42   ` rajesh.shah
2005-05-21  0:42 ` [patch 2/2] x86_64: Collect " rajesh.shah-ral2JQCrhuEAvxtiuMwx3w
2005-05-21  0:42   ` rajesh.shah
2005-05-23 16:15   ` Andi Kleen
     [not found]     ` <20050523161507.GN16164-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2005-05-24  0:57       ` Rajesh Shah
2005-05-24  0:57         ` Rajesh Shah
2005-05-24 12:05         ` Andi Kleen
2005-05-24 14:58           ` Ivan Kokshaysky
2005-05-24 15:45             ` Rajesh Shah
     [not found]               ` <20050524084533.A20567-39QZ/XbsZ5/mO6KZMuUCQVaTQe2KTcn/@public.gmane.org>
2005-05-24 16:58                 ` Ivan Kokshaysky
2005-05-24 16:58                   ` Ivan Kokshaysky
2005-05-24 17:37                   ` Rajesh Shah [this message]
     [not found]                     ` <20050524103724.A22049-39QZ/XbsZ5/mO6KZMuUCQVaTQe2KTcn/@public.gmane.org>
2005-05-26  9:34                       ` Ivan Kokshaysky
2005-05-26  9:34                         ` Ivan Kokshaysky

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=20050524103724.A22049@unix-os.sc.intel.com \
    --to=rajesh.shah@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=ink@jurassic.park.msu.ru \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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.