From: Grant Grundler <grundler@cup.hp.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Ryan Bradetich <rbradetich@uswest.net>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] RFC: I/O tree design
Date: Mon, 05 Feb 2001 10:34:48 -0800 [thread overview]
Message-ID: <200102051834.KAA02270@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Sat, 03 Feb 2001 17:57:51 PST." <20010203175751.C12985@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
...
> One advantage of doing this is that `Child' could be a pointer to a
> PCI bus.
I don't think I want that. PCI busses have their own heirarchy
and I would much rather keep them quite seperate. At least for
the moment I would. Future abstraction of native bus access
and mgt methods might make this more interesting.
> > This proposal also calls for a special "root" node at
>
> And you don't ned a root node, just siblings.
You are right - PCI starts out as a bunch of siblings too.
If it makes the code simpler to have a root node, then
I think it's ok to keep it.
Sometimes, it's convenient to think of the memory controller(s)
as the "parent" of the central bus and memory banks as children
(just like CPU would also be a child). This model works under ccNuma
as well with memory at multiple levels in the I/O tree.
Note that HPUX walks the "PA I/O tree" in a depth-first
fashion like PCI as well. So I expect the "siblings-only
for central bus" would be ok.
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-02-05 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 7:17 [parisc-linux] RFC: I/O tree design Ryan Bradetich
2001-02-03 17:57 ` Matthew Wilcox
2001-02-05 4:04 ` Ryan Bradetich
2001-02-05 18:34 ` Grant Grundler [this message]
2001-02-06 6:02 ` Matthew Wilcox
2001-02-06 7:10 ` Grant Grundler
2001-02-06 8:07 ` Grant Grundler
2001-02-05 18:22 ` Grant Grundler
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=200102051834.KAA02270@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=matthew@wil.cx \
--cc=parisc-linux@thepuffingroup.com \
--cc=rbradetich@uswest.net \
/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