| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Thu, 25 Nov 1999 15:53:43 +0100 (MET) From: Tassa Sandro <tassa@apemaia.roma1.infn.it> Reply-To: Tassa Sandro <tassa@apemaia.roma1.infn.it> To: Mailing List Linux Kernel <linux-kernel@vger.rutgers.edu> Cc: linux-scsi@vger.rutgers.edu Message-ID: <Pine.LNX.3.96.991125154844.26805A-100000@apemaia.roma1.infn.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi all, I'm studing how and 'trying to write' a scsi driver. To test driver's performance now I'm working with sg_utils < of Gilbert >. When I use sg_dd512 all work fine! But (there's always a but) when I use sg_dd2048 (on the same device with the same driver) I see that it writes and correctly reads only the first 2048 byte after that, it doesn't behave as I think: it writes and reads rubbish! Questions: Is it correct using sg_dd2048 on devices with sector size = 512? I have seen that the difference between sg_dd512 and sg_dd2048 is in the scsi cmnd (in the 'transfert lenght' field), where sg_ddXXXX writes the number of blocks. Who have to handle this value? Thanks, Sandro - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.rutgers.edu
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |