X-Account-Key: account1
X-Mozilla-Keys: 
Received: from edo.cn.fujitsu.com (10.167.33.5) by
 G08CNEXCHPEKD02.g08.fujitsu.local (10.167.33.89) with Microsoft SMTP Server
 id 14.3.181.6; Sat, 24 Oct 2015 02:52:57 +0800
Received: from heian.cn.fujitsu.com (localhost.localdomain [127.0.0.1])	by
 edo.cn.fujitsu.com (8.14.3/8.13.1) with ESMTP id t9NIqKZ7000375	for
 <caoj.fnst@cn.fujitsu.com>; Sat, 24 Oct 2015 02:52:25 +0800
X-IronPort-AV: E=Sophos;i="5.15,520,1432569600";
   d="scan'208,217";a="102209019"
Received: from nm19-vm1.access.bullet.mail.gq1.yahoo.com ([216.39.63.17])  by
 heian.cn.fujitsu.com with ESMTP; 24 Oct 2015 02:55:13 +0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bellsouth.net; s=s2048; t=1445626371; bh=arQKBlmALBt528mq496k+ymrn7rxLq/SBhUWw8iwof4=; h=From:To:References:In-Reply-To:Subject:Date:From:Subject; b=SrvSyC9iXHs5GVkedQ+ha49Ga3RxI8Z5uhLe+zbitq5HcB8KtuCqVZYUoZ3dkg2IJM42a+iWv0e90Qk18S1jbUbhKwSbvX2SsdKgy32iDZTLzitsD76oXTT2rmZuCthfhcY4NlbpWbiMqxPCBy7RH/1mxK99tOetXjAi9/wvj1rYY8JQ7AQJfO5KDWxe2eEsmBuGAvkU21xBNDcNAObvNqAAi+xPPkKFqHSbzBTUv1tVycR7Y85jU87FAaFCiWyOGMtateug+d5FgdaEQEvNgfwqC4uInTS6MMJ+tLwyoek3kiaiLLXGaj3VzyNNpxve/31g6JsqoVptgU0RGYQgZw==
Received: from [216.39.60.167] by nm19.access.bullet.mail.gq1.yahoo.com with
 NNFMP; 23 Oct 2015 18:52:51 -0000
Received: from [67.195.23.146] by tm3.access.bullet.mail.gq1.yahoo.com with
 NNFMP; 23 Oct 2015 18:52:51 -0000
Received: from [127.0.0.1] by smtp118.sbc.mail.gq1.yahoo.com with NNFMP; 23
 Oct 2015 18:52:51 -0000
X-Yahoo-Newman-Id: 594588.61665.bm@smtp118.sbc.mail.gq1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 3TMtA0QVM1l.kCmQHlBGrFsZXX.Z8X701RmsF7UJuD2BY9z
 c5TJ_CowlWgu.6ZQTwFVlNnzXZteLayBNZtVrJpLa.4oBC1c8zMHatlzCneG
 VyjVC3FAdT5Ixk2sZErLrbOMmuUnL3aHpZFWIwBe3dNt4thp8EepjFTiJ7HT
 vtvLUz2UCQ.tUUNWCh_ouTbuYmZ0k0lnWGLFOG6C9Oz8q30c_.5Mzn6HthoF
 ayTC3oIB_ssAXZC6gXj53cxEj0zQcI425XXkZV3Mp0I0uVk6RowViWt.UB1G
 MguIXhVi1Bd9fdAmAj4irNvyq64RPXDw.AHNuQ_LRUYNFD80F9.voskHnHmS
 FFCHV1DGKwBosaEcLLAac0W7vOpOg0v1TGZagNm0iUlvRqwEVkUOoUkhx7u8
 3DsMqXThNb4XLpkIS5Y7nlNqJuVDM2dQ6QSVScQ605la1yV2yGrYYUekqmSR
 npPh5Mp84kl6hv_0fTCkX8foP9BAKpIB0v24v6QnhuPzTdkBjcG50CCXv4.v
 4W9qyA8vuw60_RtiefdpMBUo6Q2zpE6dnp68fiMvqMRpXmQ--
X-Yahoo-SMTP: 2W8Z.8SswBC69ljk8iHLxrZ7pZ4jzBlYQZ8znCn3qAs-
From: Dick K. <dckly@bellsouth.net>
To: 'Cao jin' <caoj.fnst@cn.fujitsu.com>
References: <5629EE4D.7060806@cn.fujitsu.com>
In-Reply-To: <5629EE4D.7060806@cn.fujitsu.com>
Subject: RE: [Tech Support] question about ARI Device definition
Date: Fri, 23 Oct 2015 14:52:53 -0400
Message-ID: <007901d10dc4$07446910$15cd3b30$@bellsouth.net>
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_007A_01D10DA2.80344FB0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQE0WVdaDLuBJDjdUM0DMYcJVmxJzZ+yzkNw
Content-Language: en-us
Return-Path: dckly@bellsouth.net
X-MS-Exchange-Organization-AuthSource: G08CNEXCHPEKD02.g08.fujitsu.local
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AVStamp-Mailbox: SMEXutTf;1199460;0;This mail has
 been scanned by Trend Micro ScanMail for Microsoft Exchange;
X-MS-Exchange-Organization-SCL: 0
MIME-Version: 1.0

------=_NextPart_000_007A_01D10DA2.80344FB0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Please see the response in your appended note.  The response is based on =
the PCIe 3.1 spec.

Regards,
Richard
(Please send responses to this inquiry (and future technical support =
inquiries) to pcitech@pcisig.com)
Sending technical questions to administration@pcisig.com delays the =
response to the question.
----------------------------------2242  613
From: Cao jin [mailto:caoj.fnst@cn.fujitsu.com]=20
Sent: Friday, October 23, 2015 4:23 AM
To: pcitech@pcisig.com
Subject: [Tech Support] question about ARI Device definition

hello there,

     thanks for quick response to my last mail. I have a new question =
here.

     the definition of ARI Device in spec: A Device associated with an =
Upstream Port.
If I understand right, ARI device has an upstream port on the device, =
while non-ARI device don`t have.=20
***********************2242 RESPONSE:  An ARI Endpoint and a non-ARI =
Endpoint both have an Upstream Port.

But in figure 6-13 of PCIe spec 3.1, on ARI device X & Y, don`t see any =
notation of upstream port on it, should they have a notation of upstream =
port?
***********************613 RESPONSE:  it should be obvious that a device =
connected to a Root Port or switch Downstream Port must be a device with =
an Upstream Port.

and also, If I understand right, ARI device has a upstream port =
associated, so the main functionality of upstream port is routing msg to =
the functions immediately below the port?
***********************2242 RESPONSE:  The main feature of an ARI device =
is a Function Number field of 8 bits.=20
If you have any additional questions, please let us know.
=20
--
Yours Sincerely,

Cao Jin

------=_NextPart_000_007A_01D10DA2.80344FB0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"><html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<meta name=3D"Generator" content=3D"MS Exchange Server version 14.02.5004.0=
00">
<title>RE: [Tech Support] question about ARI Device definition</title>
</head>
<body>
<!-- Converted from text/rtf format -->

<p dir=3D"LTR"><span lang=3D"en-us"></span><span lang=3D"en-us"><font face=
=3D"Calibri">Please see the response in your appended note.&nbsp; The respo=
nse is based on the PCIe 3.1 spec.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">Regards,</font><=
/span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">Richard</font></=
span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">(Please send res=
ponses to this inquiry (and future technical support inquiries) to pcitech@=
pcisig.com)</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">Sending technica=
l questions to administration@pcisig.com delays the response to the questio=
n.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">----------------=
------------------</font></span><span lang=3D"en-us"></span><span lang=3D"e=
n-us"><font face=3D"Calibri">2242&nbsp; 613</font></span><span lang=3D"en-u=
s"><br>
<font face=3D"Calibri">From: Cao jin [<a href=3D"mailto:caoj.fnst@cn.fujits=
u.com">mailto:caoj.fnst@cn.fujitsu.com</a>]<br>
Sent: Friday, October 23, 2015 4:23 AM<br>
To: pcitech@pcisig.com<br>
Subject: [Tech Support] question about ARI Device definition</font></span><=
span lang=3D"en-us"></span><span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">hello there,</fo=
nt></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">&nbsp;&nbsp;&nbs=
p;&nbsp; thanks for quick response to my last mail. I have a new question h=
ere.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">&nbsp;&nbsp;&nbs=
p;&nbsp; the definition of ARI Device in spec: A Device associated with an =
Upstream Port.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">If I understand =
right, ARI device has an upstream port on the device, while non-ARI device =
don`t have.</font></span><span lang=3D"en-us"> </span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><b></b></span><span lang=3D"en-us"><b><=
font color=3D"#0070C0" face=3D"Calibri">***********************</font></b><=
/span><span lang=3D"en-us"><b></b></span><span lang=3D"en-us"><b><font colo=
r=3D"#0070C0" face=3D"Calibri">2242</font></b></span><span lang=3D"en-us"><=
b></b></span><span lang=3D"en-us"><b><font color=3D"#0070C0" face=3D"Calibr=
i"> RESPONSE:</font></b></span><span lang=3D"en-us"></span><span lang=3D"en=
-us"><font color=3D"#0070C0" face=3D"Calibri">&nbsp; An ARI Endpoint and a =
non-ARI Endpoint b</font></span><span lang=3D"en-us"></span><span lang=3D"e=
n-us"><font color=3D"#0070C0" face=3D"Calibri">o</font></span><span lang=3D=
"en-us"></span><span lang=3D"en-us"><font color=3D"#0070C0" face=3D"Calibri=
">th have an Upstream Port.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"></span><span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">But in figure 6-=
13 of PCIe spec 3.1, on ARI device X &amp; Y, don`t see any notation of ups=
tream port on it, should they have a notation of upstream port?</font></spa=
n></p>

<p dir=3D"LTR"><span lang=3D"en-us"><b></b></span><span lang=3D"en-us"><b><=
font color=3D"#0070C0" face=3D"Calibri">***********************</font></b><=
/span><span lang=3D"en-us"><b></b></span><span lang=3D"en-us"><b><font colo=
r=3D"#0070C0" face=3D"Calibri">613</font></b></span><span lang=3D"en-us"><b=
></b></span><span lang=3D"en-us"><b><font color=3D"#0070C0" face=3D"Calibri=
"> RESPONSE:</font></b></span><span lang=3D"en-us"></span><span lang=3D"en-=
us"><font color=3D"#0070C0" face=3D"Calibri">&nbsp;</font></span><span lang=
=3D"en-us"></span><span lang=3D"en-us"> <font color=3D"#0070C0" face=3D"Cal=
ibri">it should be obvious that a device connected to a Root Port or switch=
 Downstream Port must be a device with an Upstream Port.</font></span><span=
 lang=3D"en-us"></span><span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">and also, If I u=
nderstand right, ARI device has a upstream port associated, so the main fun=
ctionality of upstream port is routing msg to the functions immediately bel=
ow the port?</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><b></b></span><span lang=3D"en-us"><b><=
font color=3D"#0070C0" face=3D"Calibri">***********************</font></b><=
/span><span lang=3D"en-us"><b></b></span><span lang=3D"en-us"><b><font colo=
r=3D"#0070C0" face=3D"Calibri">2242</font></b></span><span lang=3D"en-us"><=
b></b></span><span lang=3D"en-us"><b><font color=3D"#0070C0" face=3D"Calibr=
i"> RESPONSE:</font></b></span><span lang=3D"en-us"></span><span lang=3D"en=
-us"><font color=3D"#0070C0" face=3D"Calibri">&nbsp;</font></span><span lan=
g=3D"en-us"></span><span lang=3D"en-us"> <font color=3D"#0070C0" face=3D"Ca=
libri">The main feature of an ARI device is a Functi</font></span><span lan=
g=3D"en-us"></span><span lang=3D"en-us"><font color=3D"#0070C0" face=3D"Cal=
ibri">o</font></span><span lang=3D"en-us"></span><span lang=3D"en-us"><font=
 color=3D"#0070C0" face=3D"Calibri">n Number field</font></span><span lang=
=3D"en-us"></span><span lang=3D"en-us"> <font color=3D"#0070C0" face=3D"Cal=
ibri">of 8 bits.</font></span><span lang=3D"en-us"> </span></p>

<p dir=3D"LTR"><span lang=3D"en-us"></span><span lang=3D"en-us"></span><spa=
n lang=3D"en-us"><font color=3D"#0070C0" face=3D"Calibri">If you have any a=
dditional questions, please let us know.</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font color=3D"#0070C0" face=3D"Calibri=
">&nbsp;</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">--</font></span>=
</p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">Yours Sincerely,=
</font></span></p>

<p dir=3D"LTR"><span lang=3D"en-us"><font face=3D"Calibri">Cao Jin</font></=
span></p>

</body>
</html>=

------=_NextPart_000_007A_01D10DA2.80344FB0--
