Dan Williams writes:
> On Mon, Apr 22, 2019 at 8:59 AM Jeff Moyer wrote:
>>
>> Dan Williams writes:
>>
>> > On Thu, Apr 18, 2019 at 9:18 AM Christoph Hellwig
>> > wrote:
>> >>
>> >> On Thu, Apr 18, 2019 at 09:05:05AM -0700,
Dan Williams writes:
> On Thu, Apr 18, 2019 at 9:18 AM Christoph Hellwig wrote:
>>
>> On Thu, Apr 18, 2019 at 09:05:05AM -0700, Dan Williams wrote:
>> > > > I'd either add a comment about avoiding retpoline overhead here or just
>> > > > make ->flush == NULL mean generic_nvdimm_flush(). Just so
Dan Williams writes:
> On Fri, Apr 12, 2019 at 6:12 AM Jeff Moyer wrote:
>>
>> Jan Kara writes:
>>
>> > On Thu 11-04-19 07:51:48, Dan Williams wrote:
>> >> On Tue, Apr 9, 2019 at 9:09 PM Pankaj Gupta wrote:
>> >> > + } else
Jan Kara writes:
> On Thu 11-04-19 07:51:48, Dan Williams wrote:
>> On Tue, Apr 9, 2019 at 9:09 PM Pankaj Gupta wrote:
>> > + } else {
>> > + if (nd_region->flush(nd_region))
>> > + rc = -EIO;
>>
>> Given the common case wants to be fast and synchronous
Pankaj Gupta writes:
>> Ideally, qemu (seabios?) would advertise a platform capabilities
>> sub-table that doesn't fill in the flush bits.
>
> Could you please elaborate on this, how its related to disabling
> MAP_SYNC? We are not doing entire nvdimm device emulation.
My mistake. If you're not
Dan Williams writes:
> [ adding Jeff directly since he has also been looking at
> infrastructure to track when MAP_SYNC should be disabled ]
>
> On Wed, Apr 25, 2018 at 7:21 AM, Dan Williams
> wrote:
>> On Wed, Apr 25, 2018 at 4:24 AM, Pankaj Gupta wrote:
>>> This patch adds virtio-pmem driver
