From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id BE58A986488 for ; Wed, 18 Aug 2021 08:45:49 +0000 (UTC) From: Cornelia Huck In-Reply-To: References: <20210813095216.487591-1-pankaj.gupta.linux@gmail.com> Date: Wed, 18 Aug 2021 10:45:28 +0200 Message-ID: <87tujnrviv.fsf@redhat.com> MIME-Version: 1.0 Subject: [virtio-dev] Re: [PATCH v2] virtio-pmem: PMEM device spec Content-Type: text/plain To: Pankaj Gupta , Stefan Hajnoczi Cc: virtio-dev@lists.oasis-open.org, Dan Williams , David Hildenbrand , "Michael S . Tsirkin" , Taylor Stark , Pankaj Gupta List-ID: On Tue, Aug 17 2021, Pankaj Gupta 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