[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6E21E5352C11B742B20C142EB499E0480816C460@TK5EX14MBXC126.redmond.corp.microsoft.com>
Date: Fri, 1 Jul 2011 13:01:43 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Christoph Hellwig <hch@...radead.org>
CC: "gregkh@...e.de" <gregkh@...e.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"Abhishek Kane (Mindtree Consulting PVT LTD)"
<v-abkane@...rosoft.com>, "Hank Janssen" <hjanssen@...rosoft.com>
Subject: RE: [PATCH 24/40] Staging: hv: storvsc: On I/O get the correct IDE
device
> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@...radead.org]
> Sent: Friday, July 01, 2011 4:17 AM
> To: KY Srinivasan
> Cc: Christoph Hellwig; gregkh@...e.de; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; virtualization@...ts.osdl.org; Haiyang Zhang;
> Abhishek Kane (Mindtree Consulting PVT LTD); Hank Janssen
> Subject: Re: [PATCH 24/40] Staging: hv: storvsc: On I/O get the correct IDE device
>
> On Thu, Jun 30, 2011 at 09:15:54PM +0000, KY Srinivasan wrote:
> > That is what I did initially. Then looking at the way we were handling scsi
> devices
> > where each scsi controller configured for the guest results in an emulated HBA
> > (scsi host) in the guest and all the block devices under a given controller are
> > handled through this one host, I decided to mimic a similar structure - one
> > scsi host for all the block devices configured as an IDE device.
> >
> > I can go back to my earlier implementation with one host per disk.
>
> Was there any downside you noticed from using one host per emulated
> disk?
Nothing I could see from whatever testing I did. However, the guest will have
Scsi hosts that the user did not configure. This is certainly the case in both
approaches - just the numbers are different!
K. Y
--
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