On 1/31/2018 7:01 PM, Myron Stowe wrote: >> I think from above examples: >> 1. perf mode is moving devices to 256 MPS as it can. >> 2. safe mode is setting to 128 MPS >> 3. perf mode set MRRS=MPS is a CORRECT call for device with MPSC lower than its parents. >> 4. perf mode set MRRS=MPS is not necessary for a device with SAME MPSC as its parents? >> 5. it is an interested point to me that slot/switch/root MRRS are always set to 128B, I have not found out why. > In Sinan's original posting, a reference to > https://www.xilinx.com/support/documentation/white_papers/wp350.pdf > was provided. When I read that paper and got to the "Read Completion > Boundary" section I thought to myself: "If RCB can only be 64 or 128 > bytes then what's the point of MPS (or MRRS) as all TLP completions > would be limited to 64 or 128 bytes? (see also the paper's 'Read > Completions with the RCB Set to 64 Bytes' figure)". I brought this up > to a colleague and they surmised that possibly only _lower end_ > (a.k.a. lazy) chipset implementations would truly have RCB limited > sized completions; higher end chipsets would of course have to comply > with RCB when communicating with the memory controller but could then > aggregate data into larger MPS (or MRRS) sized TLP completion packets. > Perhaps this might explain why you always saw slot/switch/root values > set at 128B? > I have looked at that paper before. It is plain wrong. Read Completion Boundary is about the alignment of addresses that an endpoint is sending in memory read packets according to the spec. It has nothing to do with the packet size. The limitation on MRRS could be that device (switch) doesn't support it. A device is allowed to reject an MRRS set value. -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
