linux-kernel - Re: [PATCH 24/40] Staging: hv: storvsc: On I/O get the correct IDE device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110701081725.GC28322@infradead.org>
Date:	Fri, 1 Jul 2011 04:17:25 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	"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

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? 
--
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/