On Thu, Jul 23, 2020 at 3:57 AM Rick Payne wrote:
>
> Trying to characterise some performance stuff, I thought I'd run socat
> under OSv however it panics:
>
> $ sudo scripts/run.py -n -e 'socat tcp4-listen:6971 open:/dev/null'OSv
> v0.55.0
> eth0: 192.168.122.76
> Booted up in 3245.70 ms
>
Hi Rick,
On Thu, Jul 23, 2020 at 4:34 AM Rick Payne wrote:
>
> Thanks, but the question was more 'why does the OSv socketpair() only
> support SOCK_STREAM, and not SOCK_DGRAM?'. I guess there has to be a
> reason why that decision was made.
>
I doubt there's any technical reason. We likely
Thanks, but the question was more 'why does the OSv socketpair() only
support SOCK_STREAM, and not SOCK_DGRAM?'. I guess there has to be a
reason why that decision was made.
As another datapoint, I removed the assert in OSv and things 'worked'
(though I can't tell if that was luck or because
Best is to put a breakpoint and start single stepping and read
those variable values
On Wed, Jul 22, 2020 at 5:57 PM Rick Payne wrote:
>
> Trying to characterise some performance stuff, I thought I'd run socat
> under OSv however it panics:
>
> $ sudo scripts/run.py -n -e 'socat
Trying to characterise some performance stuff, I thought I'd run socat
under OSv however it panics:
$ sudo scripts/run.py -n -e 'socat tcp4-listen:6971 open:/dev/null'OSv
v0.55.0
eth0: 192.168.122.76
Booted up in 3245.70 ms
Cmdline: socat tcp4-listen:6971 open:/dev/null
Assertion failed: type
