From: Cornelia Huck <cohuck@redhat.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.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 v2] virtio-pmem: PMEM device spec
Date: Wed, 18 Aug 2021 10:45:28 +0200 [thread overview]
Message-ID: <87tujnrviv.fsf@redhat.com> (raw)
In-Reply-To: <CAM9Jb+idw-LNTbEekYz9KkuYu4w+T4UbzLJoGfQULU=2Zd97ng@mail.gmail.com>
On Tue, Aug 17 2021, Pankaj Gupta <pankaj.gupta.linux@gmail.com> wrote:
>> > +\drivernormative{\subsubsection}{Driver Initialization: Virtio flush}{Device Types / PMEM Driver / Driver Initialization / Virtio flush}
>> > +
>> > +The driver MUST implement a virtio based flushing interface.
>>
>> I think this can be dropped. The only way to make writes persistent is
>> by sending flush requests. There is no need to say that the driver has
>> to use this interface. It doesn't really have to, but then it won't be
>> able to guarantee persistence.
>
> I am not 100 percent sure on this.
I don't think we want this in a normative section, but maybe there's a
place for it in a section that describes the general operation?
---------------------------------------------------------------------
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-18 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 9:52 [PATCH v2] virtio-pmem: PMEM device spec Pankaj Gupta
2021-08-17 15:26 ` Stefan Hajnoczi
2021-08-17 20:11 ` Pankaj Gupta
2021-08-18 8:45 ` Cornelia Huck [this message]
2021-08-19 5:53 ` Pankaj Gupta
2021-08-19 9:38 ` [virtio-dev] " Stefan Hajnoczi
2021-08-19 10:11 ` Pankaj Gupta
2021-08-18 9:22 ` Cornelia Huck
2021-08-19 6:03 ` 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=87tujnrviv.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=stefanha@redhat.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