[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0CE8B6BE3C4AD74AB97D9D29BD24E552011D6317@CORPEXCH1.na.ads.idt.com>
Date: Tue, 17 Aug 2010 10:47:59 -0700
From: "Bounine, Alexandre" <Alexandre.Bounine@....com>
To: "Micha Nelissen" <micha@...i.hopto.org>
Cc: <akpm@...ux-foundation.org>, <linux-kernel@...r.kernel.org>,
<linuxppc-dev@...abs.org>,
"Bounine, Alexandre" <Alexandre.Bounine@....com>
Subject: RE: [PATCH 4/9] RapidIO: Add relation links between RIO device structures
Micha Nelissen wrote:
>
> I agree it's desirable to have this information. Notes:
> 1) is rio_dev->prev used anywhere? (maybe I missed it)
It is used to scan route back when servicing an orphaned PW message.
I also see its future use when invalidating route(s) in case of device
removal.
> 2) is the nextdev[port] list complete? I mean are all connected
switches
> in the list? My guess is that multiply connected switches are
enumerated
> only once therefore only appear in the nextdev if only one switch,
> instead of all
> 3) it would be nice to have all switch connections information.
Good catch. I will address this.
> In case ever the network is rerouted, this information will become
> useful; instead of having a tree representation of the network only.
I consider proposed implementation as transitional until enumeration
logic is reworked.
It already is an attempt to move towards a tree representation. Making
switch support
available was given higher priority compared to other things needed for
RIO subsystem.
Alex.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists