<miragebot>
mirage/master ae8f400 Thomas Gazagnaire: Switch to topkg
miragebot has left #mirage [#mirage]
MK__ has quit [Quit: Leaving...]
copy` has joined #mirage
mort___1 has quit [Quit: Leaving.]
<lobo>
hi. the upgrade of mirage-types just failed with "make: *** No rule to make target 'build-types'. Stop." i'm using the mirage-dev repo. i can open a gh issue if this is not a known issue
<mato>
lobo: it's being fixed right now
<mato>
lobo: if you update your mirage-dev repo it should work now
<mato>
lobo: (i.e. your mirage-dev opam remote, so do an opam update)
<lobo>
mato: ah, thx. it worked :D
<hannes>
mato: hopefully at some point this week I'll find the time to test the solo5-freebsd-virtio-net...
<hannes>
(just kept myself busy with breaking APIs)
<mato>
hannes: ricardo and me both have freebsd boxes to test on now, so we're managing ok
<hannes>
:D
<mato>
hannes: of course more testing will help. i'm hoping that we're getting through the majority of bugs now
<hannes>
mato: did you try the virtio-block in the same run?
<mato>
hannes: no, i haven't tested that at all yet
<mato>
hannes: what i really need to do is make a proper end to end testing system of some kind, but it's not trivial.
<mato>
will get there eventually...
<hannes>
mato: automation is a bit inconvenient due to grub-bhyve imho...
<mato>
it's more about deciding what exactly needs to be tested, getting the test "results" out and reliably handling failures, timeouts and whatnot.
<mato>
that's the hard part..
rgrinberg has joined #mirage
rgrinberg has quit [Client Quit]
rgrinberg has joined #mirage
jermar has quit [Ping timeout: 244 seconds]
mort___ has quit [Quit: Leaving.]
<mato>
hannes: if you do get some free time (and mental space) it'd be worth reviewing the current virtio code (in solo5#99, not merged yet). perhaps you'll notice something we've missed that can explain the behaviour with bhyve.
<mato>
hannes: I probably won't be able to pay much attention to it for the rest of the week (off to Berlin for LinuxCon tonight)
<hannes>
mato: what is the problem with the code?
<hannes>
(I'll be travelling to berlin on wednesday evening, but not really for linuxcon... anyways, if you feel like meeting up let me know)
<hannes>
(the code in the PR that is, afaics it improves the current state!?)
mort___ has joined #mirage
jermar has joined #mirage
<mato>
hannes: Yes, the code in that PR is much better in general, we actually get data flowing both ways on bhyve.
<mato>
hannes: However, unlike on Linux, a "ping -f" is still not successful
<mato>
hannes: (Linux + QEMU/KVM)
<mato>
hannes: It *looks* like bhyve is pushing packets onto the RXQ faster than we can get around to processing them (in test_ping_serve), but that doesn't really make sense since test_ping_serve should be able to process 100pps without blinking.
<mato>
hannes: I'll be in Berlin till Sunday, so we could meet up, yeah.
<hannes>
mato: do we get one interrupt per packet (or one interrupt and then busy loop till all packets in the queue are processed)? do we wait for the ack from bhyve when sending?
<hannes>
mato: whichever day works for you, feel free to txt me (phone # in PM)
<mato>
hannes: we get one interrupt per packet, but we don't really "process" anything in the interrupt handler
<mato>
hannes: in the interrupt we just loop and update our view of how many packets there are to process
<hannes>
hmm, ic.. should be fine
<mato>
hannes: (with the changes in #98 this is all much clearer than the current master)
<hannes>
what prevents you from merging #98? obviously patches can be developed on top of that in any way..
<mato>
yeah, we should merge that, just discussing with ricardo
<mato>
(with the fixes mentioned in the last comment)
yomimono has joined #mirage
<hannes>
mato: so, does solo5-bhyve see all the received packets and fails to answer, or does it only see some of these packets?
<mato>
hannes: good point, will check. have to go now, need to pack.
<hannes>
enjoy, and safe travels
mort___ has left #mirage [#mirage]
MK__ has joined #mirage
rgrinberg has quit [Ping timeout: 265 seconds]
MK__ has quit [Remote host closed the connection]
mort___ has joined #mirage
rgrinberg has joined #mirage
smondet has quit [Ping timeout: 244 seconds]
andreas23 has quit [Quit: Leaving.]
brson has joined #mirage
mort___ has quit [Quit: Leaving.]
smondet has joined #mirage
andreas23 has joined #mirage
rgrinberg has quit [Read error: Connection reset by peer]
rgrinberg has joined #mirage
andreas23 has quit [Quit: Leaving.]
andreas23 has joined #mirage
andreas231 has joined #mirage
brson has quit [Ping timeout: 252 seconds]
andreas23 has quit [Ping timeout: 265 seconds]
brson has joined #mirage
mort___ has joined #mirage
brson has quit [Ping timeout: 252 seconds]
brson has joined #mirage
rgrinberg has quit [Ping timeout: 248 seconds]
mort___ has quit [Quit: Leaving.]
rgrinberg has joined #mirage
mort___ has joined #mirage
mort___ has quit [Client Quit]
mort___ has joined #mirage
copy` has quit [Quit: Connection closed for inactivity]