From: Bill.Martin@emulex.com Subject: clarification of meaning of transmitted in phy events Date: Thu, 15 Nov 2007 11:05:40 -0800 To: <t10@t10.org> X-Message-Number: 8250 Formatted message: HTML-formatted message In SAS2r12 table 37, there are a number of events that relate to received and transmitted primitives. Some of these e.g., code 23h Transmitted retry-class OPEN_REJECT count, and code 25h Received AIP (WAITING ON PARTIAL) count, explicitly call out whether and expander shall count forwarded versions of these primitives. The following PHY Events do not explicitly state what expanders shall do when forwarding these primitives: 40h Transmitted SSP frame count WC Number of SSP frames transmitted. 41h Received SSP frame count WC Number of SSP frames received. 44h Transmitted CREDIT_BLOCKED count WC Number of times the phy transmitted a CREDIT_BLOCKED. 45h Received CREDIT_BLOCKED count WC Number of times the phy received a CREDIT_BLOCKED. 50h Transmitted SATA frame count WC Number of STP or SATA frames transmitted. 51h Received SATA frame count WC Number of STP or SATA frames received. 60h Transmitted SMP frame count WC Number of SMP frames transmitted. 61h Received SMP frame count WC Number of SMP frames received. Bill Martin Emulex Office of Technology Industry Standards 916 772-3658 916 765-6875 (Cell) bill.martin@emulex.com