If one place is more palatable than another, we can favor that location. My first inclination would be next to the Retry Data Frames bit, which is in the basic frame header outside of the information unit portion. -- Rob Elliott, elliott@xxxxxx Hewlett-Packard Industry Standard Server Storage Advanced Technology https://ecardfile.com/id/RobElliott > -----Original Message----- > From: Moore, Eric [mailto:Eric.Moore@xxxxxxxx] > Sent: Monday, July 17, 2006 1:39 PM > To: James Bottomley; Patterson, Andrew D (Linux R&D) > Cc: dougg@xxxxxxxxxx; linux-scsi@xxxxxxxxxxxxxxx; Elliott, > Robert (Server Storage); Johnson, Steve; Rivera, Peter; > Besmer, Brad; Shirron, Stephen > Subject: RE: [PATCH 1/10] mptfusion : Transport Layer Retry support > > On Friday, July 14, 2006 5:25 PM, James Bottomley wrote: > > I have no idea about the fusion ... the frame control is > > embedded deeply > > in the firmware, so I think it would probably require a firmware > > upgrade. Eric can comment on this better than I. > > > > Yes, frame creation is in the firmware, not driver. > Currently the linux driver knows TLR is implmented in firmware by > looking > at IOCFacts->IOCCapabilities (bit 11). > > From sas2r04a.pdf, section 9.2.1 ssp_frame_format, there is > RETRY_DATA_FRAME (byte 10, bit 2) - write data frames retried > (xfer_rdy) > RETRANSMIT (byte 10, bit 1) - control frame retried (task, response, > xfer_rdy) > > Rob Elliot wrote: "the initiator could set a similar bit in > COMMAND and TASK frames to let the target know that it is > safe to retry frames for the whole command." > > Which bit is in consideration for being set? In the ssp frame > header or > IU? > >
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
