Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753648AbZIAQr3 (ORCPT ); Tue, 1 Sep 2009 12:47:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751901AbZIAQr2 (ORCPT ); Tue, 1 Sep 2009 12:47:28 -0400 Received: from smtp-outbound-1.vmware.com ([65.115.85.69]:50908 "EHLO smtp-outbound-1.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751768AbZIAQr1 (ORCPT ); Tue, 1 Sep 2009 12:47:27 -0400 Subject: Re: [PATCH] SCSI driver for VMware's virtual HBA. From: Alok Kataria Reply-To: akataria@vmware.com To: Boaz Harrosh Cc: Matthew Wilcox , Alok Kataria , James Bottomley , Robert Love , Randy Dunlap , Mike Christie , "linux-scsi@vger.kernel.org" , LKML , Andrew Morton , Dmitry Torokhov , Rolf Eike Beer , Maxime Austruy , Bhavesh Davda In-Reply-To: <4A9D49CE.6080600@panasas.com> References: <1251415060.16297.58.camel@ank32.eng.vmware.com> <1251739735.16169.20.camel@ank32.eng.vmware.com> <1251741624.18828.83.camel@mulgrave.site> <1251755593.16169.51.camel@ank32.eng.vmware.com> <1251815012.3864.55.camel@mulgrave.site> <35f686220909010908k24f0164nc09b1158b6841ff3@mail.gmail.com> <20090901161306.GN22870@parisc-linux.org> <4A9D49CE.6080600@panasas.com> Content-Type: text/plain Organization: VMware INC. Date: Tue, 01 Sep 2009 09:47:29 -0700 Message-Id: <1251823649.16169.123.camel@ank32.eng.vmware.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-8.el5_2.3) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1121 Lines: 30 On Tue, 2009-09-01 at 09:20 -0700, Boaz Harrosh wrote: > On 09/01/2009 07:13 PM, Matthew Wilcox wrote: > > > > Umm, we do share code between SCSI drivers. We have the ULDs (sg, sd, > > sr, etc), we have the midlayer, and we have the transport classes (spi, > > iscsi, fc, etc). > > > > This makes a tons of sense. a scsi_transport_paravirt can have lots of common > nubs. I bet administrators would love such common management facility. I don't see how it will help a user. VMware exports a PCI device, and this device will be available only when running under a VMware hypervisor. If a particular device is available the OS will use the corresponding driver. Please note these drivers will be used by the guest operating system, which is running virtualized. I don't get what kind of control the administrator has on this ? can you please elaborate. Alok > > Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/