Re: [PATCH V6] virtio-transport: Add a new section to clarify transport requirements

["Michael S. Tsirkin" <mst@redhat.com>]

On Thu, Jul 11, 2024 at 12:51:28PM +0530, Viresh Kumar wrote:
> On 26-06-24, 08:11, Viresh Kumar wrote:
> > On 25-06-24, 16:51, Matias Ezequiel Vara Larsen wrote:
> > > > +\section{Device Requirements}\label{sec:Creating New Transports / Device Requirements}
> > > > +
> > > > +The device keeps any data associated with a device-initiated transaction
> > > > +accessible to the driver until the driver acknowledges the transaction
> > > > +to be complete.
> > > > +
> > > > +The device doesn't access the contents of a virtqueue before the driver
> > > > +notifies, in a transport defined way, the device that the virtqueue is
> > > > +ready to be accessed.
> > > > +
> > > > +The device doesn't access or modify buffers on a virtqueue after it has
> > > > +notified the driver about their availability.
> > > > +
> > > 
> > > Why are the last two requirements in this section? Are not these
> > > requirements independent of the transport layer?
> > 
> > Hmm, maybe you are right. Cornelia ?
> 
> Hi Michael / Cornelia,
> 
> Can we please get this merged a bit sooner ? It has taken a huge
> amount of time to get this upstream. I posted the first version on
> 5th December :(
> 
> Please see if we can get done with it a bit sooner. Thanks.

Iterate faster then.
Are you going to address Matias's comments?

-- 
MST