OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [virtio-dev] [PATCH v2 1/2] content: add virtio file system device


On 13/02/19 07:33, Stefan Hajnoczi wrote:
> +Notifications are different from normal requests because they only contain
> +device writable fields.  The driver sends notification replies on one of the
> +request queues.  The format of notification requests is as follows:
> +
> +\begin{lstlisting}
> +struct virtio_fs_notification_req {
> +        // Device-writable part
> +        struct fuse_out_header out;
> +        u8 dataout[];
> +};
> +\end{lstlisting}
> +
> +\field{out} is the completion header common to all types of FUSE requests.  The
> +\field{out.unique} field is 0 and the \field{out.error} field contains a
> +FUSE_NOTIFY_* code.
> +
> +\field{dataout} consists of request-specific data, if any.  This is identical
> +to the data written to the /dev/fuse device by a FUSE daemon.
> +

What happens if notifications are lost because no request was there?
virtio-scsi has a flag for that, would it make sense to add it here too?

Paolo


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]