[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [virtio-dev] VIRTIO_BLK_F_CONFIG_WCE removed from virtio 1.0?
On Thu, Jul 02, 2015 at 09:10:42AM +0200, Paolo Bonzini wrote: > > > On 02/07/2015 07:08, Michael S. Tsirkin wrote: > > On Wed, Jul 01, 2015 at 11:50:19PM +0200, Paolo Bonzini wrote: > >> I guess we were a bit overzealous in removing VIRTIO_BLK_F_FLUSH aka > >> VIRTIO_BLK_F_WCE. The VIRTIO_BLK_F_CONFIG_WCE is a useful feature and > >> should be preserved in order to achieve feature parity between 0.9 and 1.0. > >> > >> Sorry for commenting on this so close to the deadline, but I think this > >> is a blocker. :( I'll send a patch shortly. > >> > >> Paolo > > > > Yes but it's been like this since CS01, correct? > > I would rather release CS03 as is, work on CS04 > > in parallel. > > > > Do you agree? > > It's the same. More precisely, I think it is a blocker for starting to > work on 1.1. Well we can just fork and work on it in parallel, as long as it's a single patch I don't think it's a blocker in that sense. The timeline works out like this. If we release CS03 as is, then: - 1 week to prepare a standard - 1 week to vote on publishing CS03 - 2 weeks to publish CS03 out end of July, then we start on CS04: - 1 week to prepare a draft - 1 week to vote on starting the public review - 2 weeks to start the public review - 2 weeks public review And assuming nothing else surfaces: - 1 week to prepare a standard - 1 week to vote on publishing CS03 - 2 weeks to publish CS04 out mid October. If we create CSPRD05 and start the public review for that: - 1 week to prepare a draft - 1 week to vote on starting the public review - 2 weeks to start the public review - 2 weeks public review And assuming nothing else surfaces: - 1 week to prepare a standard - 1 week to vote on publishing CS03 - 2 weeks to publish CS03 out mid September. It looks doing CS04 is a win. > > Also - maybe we can bring back scsi command support as well? > > No, SCSI command was a bad feature to begin with (a hack due to lack of > virtio-scsi). It has been deprecated years ago, and cannot be done > compatibly because it relies on the framing of buffers. This feature is > new and useful for performance. > > > Also - pls open an issue tracker. > > Done, VIRTIO-144. > > Paolo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]