linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Yang <weiyang@linux.vnet.ibm.com>
To: linux-pci@vger.kernel.org
Cc: bhelgaas@google.com
Subject: Does my understanding correct?
Date: Fri, 27 Apr 2012 17:27:04 +0800	[thread overview]
Message-ID: <20120427092704.GA22529@richard> (raw)

All, 

I draw a picture about the physical layout on a part of the pci system.

Each block represent a bridge or a device.
Am I correct?
   
    +-----------------------------+
    |                             |
    |                             |
    |      Bus#2                  |
    |   ------------------        |
    |                             |
    |                             |
    |                             |
    |               +-------------+
    |               |DownStream   |02:00.0 pci_dev
    +---------------+-------+-----+
                            |   Bus#3
             ---------------+------------------------------------------+---
                            |                                          |
                            |                                          |
    +---------------+-------+-----+               +---------------+----+--+-----+
    |               |UpStream     |03:00.0        |               |UpStream     |03:01.0
    |               +-------------+               |               +-------------+ a normal device
    |                             |               |                             |
    |                             |               |                             |
    |             Bus#4           |               |                             |
    |     -------------------     |               |                             |
    |                  +----------+               |                             |
    |                  |DownStream|               |                             | 
    +-----------------------+-----+               +-----------------------------+                       
                            |                                                 
                            | Bus#5                               
                ------------+------------                                                               


-- 
Richard Yang
Help you, Help me


             reply	other threads:[~2012-04-27  9:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27  9:27 Richard Yang [this message]
2012-04-27 14:10 ` Does my understanding correct? Jiang Liu
2012-04-27 15:55   ` Bjorn Helgaas
2012-04-27 14:17 ` Bjorn Helgaas
2012-04-28  5:01   ` Richard Yang
2012-04-28  7:21     ` Richard Yang
2012-04-30 15:56     ` Bjorn Helgaas
2012-05-02  6:24       ` Richard Yang
2012-05-02 14:59         ` Bjorn Helgaas
2012-05-02 21:05           ` Don Dutile
2012-05-03  6:21           ` Richard Yang
2012-05-03 16:39             ` Bjorn Helgaas
2012-05-04  2:11               ` Richard Yang
2012-05-06 15:21               ` Richard Yang
2012-05-07  3:00               ` Richard Yang
2012-04-28  8:21   ` Richard Yang

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=20120427092704.GA22529@richard \
    --to=weiyang@linux.vnet.ibm.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.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).