Monday, 2020-06-01

*** ailan__ has joined #kata-dev07:04
*** pcaruana has joined #kata-dev07:14
*** davidgiluk has joined #kata-dev08:03
*** ailan__ has quit IRC08:17
*** ailan__ has joined #kata-dev08:17
*** jodh has joined #kata-dev08:21
*** ailan__ has quit IRC08:38
kata-irc-bot<james.o.hunt> Any rustaceans out there who could help review https://github.com/kata-containers/kata-containers/pull/223 and https://github.com/kata-containers/kata-containers/pull/225?09:01
*** devimc has joined #kata-dev12:07
*** devimc has quit IRC13:19
*** devimc has joined #kata-dev13:19
*** crobinso has joined #kata-dev13:41
*** pcaruana has quit IRC13:44
kata-irc-bot<simon.kaegi> ah ok... thanks @eric.ernst just figured out that part is sort of mandatory ;) I'm going to see what happens if I merge the changes https://gitlab.com/virtio-fs/linux/-/commits/virtio-fs-dev/ into a recent 5.6. I noticed that at the overlayfs-next stuff seems to be merged already. Is there "any way" to support virtiofs without the dax changes?13:45
*** pcaruana has joined #kata-dev13:45
kata-irc-bot<simon.kaegi> At a glance it looked like the overlayfs stuff was merged in but there is still a bunch of DAX stuff that is not. e.g. all the changes from 9 Apr 2020 here -- https://gitlab.com/virtio-fs/linux/-/commits/virtio-fs-dev/ apart from the top commit. I'm out of my league here but am looking at what merging those changes on current 5.6 will look like.13:48
*** pcaruana has quit IRC13:49
*** pcaruana has joined #kata-dev13:50
kata-irc-bot<fidencio> Hey! We do support virtiofs without the dax changes14:02
kata-irc-bot<fidencio> Do you still have the config I shared with you?14:02
kata-irc-bot<fidencio> If you set `virtio_fs_cache_size = 0` dax won't be used and you're fine and good to go14:03
*** dklyle has joined #kata-dev14:14
kata-irc-bot<eric.ernst> Yes.14:16
kata-irc-bot<eric.ernst> Performance just suffers, that’s all.14:16
kata-irc-bot<eric.ernst> To clarify; what part is mandatory?14:16
*** pcaruana has quit IRC14:49
*** pcaruana has joined #kata-dev14:49
kata-irc-bot<simon.kaegi> ok awesome thanks!! will try14:49
kata-irc-bot<simon.kaegi> Also looks like the overlayfs stuff is only in 5.7 at least at first glance14:50
kata-irc-bot<fidencio> I can double check with Vivek, but it seems to be merged on 5.614:53
kata-irc-bot<simon.kaegi> thanks, I'm just looking at the diffs and it very well might be as I don't understand the core of what was added14:56
*** jugs1 has quit IRC15:20
*** jugs1 has joined #kata-dev15:28
kata-irc-bot<simon.kaegi> ... and success -- thanks15:35
kata-irc-bot<simon.kaegi> Let me try the overlay support15:35
davidgilukeric.ernst: DAX is not mandatory15:36
kata-irc-bot<fidencio> Cool! If something goes wrong, let us know,15:36
kata-irc-bot<simon.kaegi> perf for my test was a little slower than with dax but still much much better than for 9p15:36
kata-irc-bot<simon.kaegi> ... and you're totally right -- overlayfs work in 5.6.1515:40
kata-irc-bot<simon.kaegi> woot!15:40
kata-irc-bot<simon.kaegi> I am "super" happy with this15:40
kata-irc-bot<fidencio> \o/15:42
kata-irc-bot<simon.kaegi> So... I obviously have a ton of testing to do now... but this is starting to look really good.15:44
kata-irc-bot<simon.kaegi> I'm still using the virtiofs-dev qemu so next step is to switch over to 5.015:44
*** sameo has joined #kata-dev16:42
*** dklyle has quit IRC17:23
*** dklyle has joined #kata-dev17:23
kata-irc-bot<simon.kaegi> It turns out none of it is. I just needed to set virtio_fs_cache_size = 0. In terms of perf loss in my simple `dd` test on one of our managed bare metal kubernetes nodes I'm getting: 1. default (runc) -- 185 MB/s    --- [100%] 2. kata-qemu -- 105 MB/s   --- [56%] 3. kata-qemu-virtiofs -- 165 MB/s  --- [89%] 4. kata-clh -- 175 MB/s --- [95%] 5. kata-qemu-virtiofs-nodax -- 157 MB/s --- [85%]17:42
*** sunnycai has joined #kata-dev17:46
*** jodh has quit IRC18:00
devimc@simon.kaegi are you interested on IO performance?18:20
kata-irc-bot<simon.kaegi> definitely but currently we're using 9p so even no dax virtiofs is a giant improvement18:21
devimcmight be you want to take a look to this https://github.com/intel/pmem-csi18:21
devimckata already supports pmem devices18:21
davidgiluksimon.kaegi: The DAX trick works better for some stuff than others; it's bad for huge sequentials - it's much better when you have a reasonably small working set - one that fits in the cache size you set18:41
fidenciodevimc: do you recall some issue with OpenShift and getting the stats from the kata pods? or whether it should be working with shimv2?19:07
devimcfidencio: stats?  like cadvisor stats?19:08
devimcfidencio: I guess you are facing issues with IO and network stats19:10
fidenciodevimc: like cadvisor stats, but AFAIU cadvisor is not supposed to work and cri-stats should be the ones used19:10
fidenciodevimc: yep19:11
devimcfidencio: I guess you are using 9p .. ?19:11
fidenciodevimc: never!19:11
devimcmmm19:11
devimcis sandbox_cgroup_only true?19:12
fidenciodevimc: I know that if k8s get crio.sock as the runtime_endpoint, it'll fallback do cadvisor .. and I've changed that on both crio.conf and kubelet19:12
fidenciosandbox_cgroup_only=true, yes19:13
devimcfidencio: take a look to this https://github.com/kata-containers/runtime/issues/240019:16
*** crobinso has quit IRC19:16
fidenciodevimc: hmmm. seems to be related but still reproducible with virtiofs19:21
*** davidgiluk has quit IRC19:23
fidenciodevimc: if I'm going to report that upstream to keep track of what we're doing, would you prefer to have that to extend 2400 or as new issue?19:54
devimcfidencio: feel free to raise a new issue, we can close it later if it's duplicated19:55
fidenciodevimc: okkie19:55
*** sameo has quit IRC20:45
*** sameo has joined #kata-dev20:47
*** th0din has quit IRC20:51
*** th0din has joined #kata-dev20:52
*** th0din has quit IRC20:54
*** devimc has quit IRC20:56
*** th0din has joined #kata-dev21:18

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!