From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Hank Janssen <hjanssen@microsoft.com>,
"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
linux-kernel@vger.kernel.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: hv block drivers
Date: Mon, 30 Aug 2010 09:17:42 -0700 [thread overview]
Message-ID: <4C7BD9A6.1090108@goop.org> (raw)
In-Reply-To: <201008301643.42253.arnd@arndb.de>
On 08/30/2010 07:43 AM, Arnd Bergmann wrote:
> Hi Hank,
>
> I wanted to follow up on the block device driver discussion we had at
> LinuxCon, based on some other input I got.
>
> What most people recommended was to make both the hv scsi and the
> hv ata code scsi device drivers, *not* make them standalone block
> drivers as I originally recommended.
>
> The main reason for this is consistent naming of the devices. We
> have a lot of user code that can deal with /dev/sd* devices, but
> introducing the /dev/vd* devices for virtio caused a lot of pain
> that you probably shouldn't have to go through.
We're having the same kind of problem with the Xen xvdX device naming.
For a fully PV system it doesn't matter to much, but when you've got PV
drivers taking the place of a regular emulated hardware device it would
be nice to have a similar device name.
But there isn't a lot of similarity between the Xen block interface and
SCSI beyond the basic block transfer bits, so I was wondering how good a
match it would really be.
Have you investigated making virtio a scsi device?
J
next prev parent reply other threads:[~2010-08-30 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 14:43 hv block drivers Arnd Bergmann
2010-08-30 16:17 ` Jeremy Fitzhardinge [this message]
2010-08-30 17:08 ` Arnd Bergmann
2010-08-30 17:31 ` Hank Janssen
2010-08-30 17:35 ` Jeremy Fitzhardinge
2010-08-30 19:18 ` Arnd Bergmann
2010-08-31 10:46 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C7BD9A6.1090108@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=arnd@arndb.de \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=virtualization@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox