From: Cornelia Huck <cohuck@redhat.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Cc: virtio-dev@lists.oasis-open.org,
Dan Williams <dan.j.williams@intel.com>,
David Hildenbrand <david@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Taylor Stark <tstark@linux.microsoft.com>,
Pankaj Gupta <pankaj.gupta@ionos.com>
Subject: [virtio-dev] Re: [PATCH RESEND] virtio-pmem: PMEM device spec
Date: Tue, 03 Aug 2021 10:26:38 +0200 [thread overview]
Message-ID: <87mtpzylvl.fsf@redhat.com> (raw)
In-Reply-To: <CAM9Jb+jAbBrsQbR8hHFcskqXojj47kMc0xzivQMH0Ax2uUb8ng@mail.gmail.com>
On Fri, Jul 30 2021, Pankaj Gupta <pankaj.gupta.linux@gmail.com> wrote:
>> > +Also, configures a flush callback function with the corresponding region.
>>
>> Not sure if that is too specific already... maybe something like "Also,
>> it configures a notification for when the corresponding region is flushed."?
>
> Maybe will remove this line altogether as it is implementation
> details?
Maybe... I think the point is to configure _something_, not sure if we
can really generalize that. Other ideas welcome.
>> See above for "flush callback". I'm mostly worrying about the wording
>> being generic enough (even though it's probably obvious enough for
>> non-Linux people as well.)
>
> yes, Something below is better?
>
> The driver MUST not enable any explicit FLUSH on the file memory
> mapped from the Virtio pmem device
Hm, not sure. Would like to see feedback from others that had worked in
this area.
>
>>
>> > +
>> > +\subsection{Driver Operations}\label{sec:Device Types / PMEM Driver / Driver Operation}
>> > +\drivernormative{\subsubsection}{Driver Operation: Virtqueue command}{Device Types / PMEM Driver / Driver Operation / Virtqueue command}
>> > +
>> > +Driver MUST send VIRTIO_FLUSH command on request virtqueue, allows guest userspace process to perform IO operations asynchronously.
>>
>> s/Driver/The driver/
>>
>> I don't think we should refer to "guest userspace" in the spec; can we
>> reword this?
>
> Sure
>
> Driver MUST send VIRTIO_FLUSH command on request virtqueue, thus
> allows asynchronous FLUSH operation on the files present in Virtio
> pmem device.
s/Driver/The driver/
s/allows/allowing/
I'm not sure whether we should refer to 'files'.
Again, feedback from others welcome; this is not really one of my core topics.
>
>>
>> > +
>> > +Driver SHOULD handle multiple fsync requests on files present on the device.
>>
>> s/Driver/The driver/
>
> o.k
>
>>
>> Again, a bit unsure on whether this is generic enough.
>
> Driver SHOULD handle multiple FLUSH requests on the files present on
> the Virtio pmem device.
Same here. I'm afraid this is not easy :(
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2021-08-03 8:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 15:04 [PATCH RESEND] virtio-pmem: PMEM device spec Pankaj Gupta
2021-07-30 11:53 ` [virtio-dev] " Cornelia Huck
2021-07-30 12:25 ` Pankaj Gupta
2021-08-03 8:26 ` Cornelia Huck [this message]
2021-08-03 8:50 ` David Hildenbrand
2021-08-03 9:02 ` Pankaj Gupta
2021-08-03 9:16 ` Pankaj Gupta
2021-08-03 9:17 ` David Hildenbrand
2021-08-04 11:07 ` [virtio-dev] " Stefan Hajnoczi
2021-08-04 11:11 ` David Hildenbrand
2021-08-04 12:33 ` Stefan Hajnoczi
2021-08-04 12:42 ` Pankaj Gupta
2021-08-04 22:58 ` Taylor Stark
2021-08-05 15:22 ` Stefan Hajnoczi
2021-08-04 11:28 ` Pankaj Gupta
2021-08-04 12:36 ` Stefan Hajnoczi
2021-08-04 12:40 ` Pankaj Gupta
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=87mtpzylvl.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=pankaj.gupta.linux@gmail.com \
--cc=pankaj.gupta@ionos.com \
--cc=tstark@linux.microsoft.com \
--cc=virtio-dev@lists.oasis-open.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