[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1251823649.16169.123.camel@ank32.eng.vmware.com>
Date: Tue, 01 Sep 2009 09:47:29 -0700
From: Alok Kataria <akataria@...are.com>
To: Boaz Harrosh <bharrosh@...asas.com>
Cc: Matthew Wilcox <matthew@....cx>,
Alok Kataria <alokkataria1@...il.com>,
James Bottomley <James.Bottomley@...e.de>,
Robert Love <robert.w.love@...el.com>,
Randy Dunlap <randy.dunlap@...cle.com>,
Mike Christie <michaelc@...wisc.edu>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Dmitry Torokhov <dtor@...are.com>,
Rolf Eike Beer <eike-kernel@...tec.de>,
Maxime Austruy <maustruy@...are.com>,
Bhavesh Davda <bhavesh@...are.com>
Subject: Re: [PATCH] SCSI driver for VMware's virtual HBA.
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists