From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Kvasnica Subject: Re: vscsi 2TB patches Date: Mon, 24 Jan 2011 13:24:28 +0100 Message-ID: <4D3D6F7C.2000903@list.ims.co.at> References: <4D222D71.9020508@list.ims.co.at><20110103230621.GP2754@reaktio.net><4D230357.3070604@list.ims.co.at><4D2316D5020000780002A2F1@vpn.id2.novell.com><4D231AA0.8060500@list.ims.co.at><4D2329BA020000780002A32F@vpn.id2.novell.com> <4D231F6C.50309@list.ims.co.at> <4D358B67020000780002CDC7@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D358B67020000780002CDC7@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: kama@jp.fujitsu.com, t.horikoshi@jp.fujitsu.com, xen-devel@lists.xensource.com, Samuel Kvasnica List-Id: xen-devel@lists.xenproject.org On 01/18/2011 12:45 PM, Jan Beulich wrote: > ack this (given the lack of a response from the > original authors, and after looking over it again), when I noticed > an apparent inconsistency: {READ,WRITE}_{6,10,16} are all > un-commented now in scsiback_emulation_init(), but > {READ,WRITE}_12 remain commented. Why Jan, I'm very sorry for the long delay, too many critical issues in progress here... Well, I did enable (lets hope) everything, the linux scsi drivers are apparently using. I've put debug printfs into the frontend driver, which has lead to several commands like READ16. I did real tests using 2 LSI U320 scsi controllers with multipathing and an attached Eonstor RaidArray + tests using the Ultrium LTO3 Autoloader + bacula. Additionally, I enabled several other SCSI commands found in other scsi drivers like "sr". I don't quite understand why the original authors excluded so many commands (thats what I state in my patch header) and hence I included only what was needed. Excluding makes sense only when emulation is needed but did not want to enable too much...