Open Stack

Sorry we hadn't test DAX much before because we have not enabled it for 
container storages in our environment.

I agree with the suggestion disable it by default. However, I don't think we
will officially support non-LTS kernels like 5.6, and I wonder whether the 
patches could be back ported to 5.4 LTS if they could fix the crash.

Xu


------------------------------------------------------------------
From:Fabiano Fidêncio <fidencio at redhat.com>
Send Time:2020年10月6日(星期二) 16:46
To:"Shinde, Archana M" <archana.m.shinde at intel.com>
Cc:kata-dev <kata-dev at lists.katacontainers.io>
Subject:Re: [kata-dev] Dax enablement in 2.0

Archana,

[...]

> In addition, we are using a 5.6 kernel with Dax patches by default for virtiofs for both qemu-virtiofs and cloud-hypervisor. I propose we instead switch to the LTS 5.4 upstream kernel that has all the bits for virtiofs except Dax. If some user wants to use dax, they can switch to the experimental 5.6 kernel instead.

I agree with the suggestion. However, I'd like to know whether it'd be
possible to have a jenkins job, running weekly or so, with a 5.6
kernel with all the new bits enabled there, as with this we could:
1. Ensure we don't break anything on the Kata side related to DAX;
2. Ensure we do at least some test to early report issues to virtio-fs folks;

Is this a reasonable and feasible approach?

[...]

Best Regards,
-- 
Fabiano Fidêncio


_______________________________________________
kata-dev mailing list
kata-dev at lists.katacontainers.io
http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.katacontainers.io/pipermail/kata-dev/attachments/20201008/c410d617/attachment.html>