From: Matt Porter <mporter@kernel.crashing.org>
To: Zhang Wei <Wei.Zhang@freescale.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] Add multi mport support.
Date: Tue, 5 Feb 2008 10:29:42 -0600 [thread overview]
Message-ID: <20080205162942.GB20177@gate.crashing.org> (raw)
In-Reply-To: <ABF87B0B6A38C0458E319AC973ED68AEBD0697@zch01exm26.fsl.freescale.net>
On Thu, Jan 31, 2008 at 02:30:13PM +0800, Zhang Wei wrote:
> > -----Original Message-----
> > From: Kumar Gala [mailto:galak@kernel.crashing.org]
> > when we have multiple ports are the device IDs on the ports intended
> > to be unique only to a port or unique across all ports?
> >
> I consider each RIO controller will has its own network, the device IDs
> should be
> unique only in its port network.
This is a bad assumption IMHO. It pushes policy on to the system
designer of a RapidIO network.
It is very possible to use multiple controllers as entry points
in a single RapidIO network fabric space. The reason one would do this
is to provide optimized paths to some endpoints in the system.
If possible, there should never be a policy assumption like this in
kernel space. It's much better to assume that one may or may not
have a unique id space.
-Matt
WARNING: multiple messages have this Message-ID (diff)
From: Matt Porter <mporter@kernel.crashing.org>
To: Zhang Wei <Wei.Zhang@freescale.com>
Cc: Kumar Gala <galak@kernel.crashing.org>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] Add multi mport support.
Date: Tue, 5 Feb 2008 10:29:42 -0600 [thread overview]
Message-ID: <20080205162942.GB20177@gate.crashing.org> (raw)
In-Reply-To: <ABF87B0B6A38C0458E319AC973ED68AEBD0697@zch01exm26.fsl.freescale.net>
On Thu, Jan 31, 2008 at 02:30:13PM +0800, Zhang Wei wrote:
> > -----Original Message-----
> > From: Kumar Gala [mailto:galak@kernel.crashing.org]
> > when we have multiple ports are the device IDs on the ports intended
> > to be unique only to a port or unique across all ports?
> >
> I consider each RIO controller will has its own network, the device IDs
> should be
> unique only in its port network.
This is a bad assumption IMHO. It pushes policy on to the system
designer of a RapidIO network.
It is very possible to use multiple controllers as entry points
in a single RapidIO network fabric space. The reason one would do this
is to provide optimized paths to some endpoints in the system.
If possible, there should never be a policy assumption like this in
kernel space. It's much better to assume that one may or may not
have a unique id space.
-Matt
next prev parent reply other threads:[~2008-02-05 16:30 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 10:30 [PATCH 1/6] Change RIO function mpc85xx_ to fsl_ Zhang Wei
2008-01-30 10:30 ` Zhang Wei
2008-01-30 10:30 ` [PATCH 2/6] Add RapidIO option to kernel configuration Zhang Wei
2008-01-30 10:30 ` Zhang Wei
2008-01-30 10:30 ` [PATCH 3/6] Move include/asm-ppc/rio.h to include/asm-powerpc/rio.h Zhang Wei
2008-01-30 10:30 ` Zhang Wei
2008-01-30 10:30 ` [PATCH 4/6] Add multi mport support Zhang Wei
2008-01-30 10:30 ` Zhang Wei
2008-01-30 10:30 ` [PATCH 5/6] Add OF-tree support to RapidIO controller driver Zhang Wei
2008-01-30 10:30 ` Zhang Wei
2008-01-30 10:30 ` [PATCH 6/6] Change the kernel configurated RapidIO system size to auto-probing Zhang Wei
2008-01-30 10:30 ` Zhang Wei
2008-02-05 16:43 ` Matt Porter
2008-02-05 16:43 ` Matt Porter
2008-02-05 5:44 ` [PATCH 5/6] Add OF-tree support to RapidIO controller driver Stephen Rothwell
2008-02-05 5:44 ` Stephen Rothwell
2008-02-05 16:06 ` Kumar Gala
2008-02-05 16:06 ` Kumar Gala
2008-02-18 7:24 ` Zhang Wei
2008-02-18 7:24 ` Zhang Wei
2008-01-30 14:27 ` [PATCH 4/6] Add multi mport support Kumar Gala
2008-01-30 14:27 ` Kumar Gala
2008-01-31 5:57 ` Zhang Wei
2008-01-31 5:57 ` Zhang Wei
2008-01-31 6:15 ` Kumar Gala
2008-01-31 6:15 ` Kumar Gala
2008-01-31 6:20 ` Kumar Gala
2008-01-31 6:20 ` Kumar Gala
2008-01-31 6:30 ` Zhang Wei
2008-01-31 6:30 ` Zhang Wei
2008-01-31 18:35 ` Phil Terry
2008-01-31 18:35 ` Phil Terry
2008-02-01 4:06 ` Zhang Wei
2008-02-01 4:06 ` Zhang Wei
2008-02-05 16:29 ` Matt Porter [this message]
2008-02-05 16:29 ` Matt Porter
2008-02-18 7:33 ` Zhang Wei
2008-02-18 7:33 ` Zhang Wei
2008-02-05 16:23 ` Matt Porter
2008-02-05 16:23 ` Matt Porter
2008-01-30 14:20 ` [PATCH 3/6] Move include/asm-ppc/rio.h to include/asm-powerpc/rio.h Kumar Gala
2008-01-30 14:20 ` Kumar Gala
2008-01-31 3:36 ` Zhang Wei
2008-01-31 3:36 ` Zhang Wei
2008-01-30 14:43 ` [PATCH 1/6] Change RIO function mpc85xx_ to fsl_ Kumar Gala
2008-01-30 14:43 ` Kumar Gala
2008-01-31 6:04 ` Zhang Wei
2008-01-31 6:04 ` Zhang Wei
2008-01-31 6:15 ` Kumar Gala
2008-01-31 6:15 ` Kumar Gala
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=20080205162942.GB20177@gate.crashing.org \
--to=mporter@kernel.crashing.org \
--cc=Wei.Zhang@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 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.