Re: [osv-dev] Re: raw socket support ?

2020-07-23 Thread Vladislav Zolotarov
On 7/23/20 5:38 AM, Nadav Har'El wrote: On Thu, Jul 23, 2020 at 12:05 PM Rick Payne > wrote: Another alternative (for me and maybe others) would be to have a standard way to hook packets direct from the virtio interface. We did have something like

[osv-dev] Adding floating-point support to AArch64 port and upgrading musl

2020-07-23 Thread Waldek Kozaczuk
Hi, As I have been researching what it would take to add floating-point support to the AArch64 port, I started realizing that it might be better (not necessarily easier) to upgrade musl. At first, I hoped I could just add fegetenv support (https://linux.die.net/man/3/fegetenv) by adding fenv.S

Re: [osv-dev] Re: raw socket support ?

2020-07-23 Thread Vinicius Fulber Garcia
Very nice ideas! Take control of the VirtIO interfaces, as Rick and Nadav suggested, can be a good solution for me too. In my particular case, I have a management interface that DHCPs, but the other interfaces (that are used for the data plane) are isolated and manually configured. I will

Re: [osv-dev] Re: raw socket support ?

2020-07-23 Thread Rick Payne
On Thu, 2020-07-23 at 12:38 +0300, Nadav Har'El wrote: > We also had until recently something more general, "assigned virtio", > where the application > gets access directly to the viritio rings (and needs to work with > them - the kernel doesn't > touch them any more). Waldek recently removed it

Re: [osv-dev] Re: raw socket support ?

2020-07-23 Thread Nadav Har'El
On Thu, Jul 23, 2020 at 12:05 PM Rick Payne wrote: > > Another alternative (for me and maybe others) would be to have a > standard way to hook packets direct from the virtio interface. > We did have something like that in the past, and I remember Vlad used it to write some sort of

Re: [osv-dev] Re: raw socket support ?

2020-07-23 Thread Rick Payne
Another alternative (for me and maybe others) would be to have a standard way to hook packets direct from the virtio interface. Especially if we could ensure that we don't dhcp on that interface. For instance, setup 2 interfaces from the host - 1 for OSv-y stuff, and one just for an application

Re: [osv-dev] Problems with socat

2020-07-23 Thread Nadav Har'El
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 >

Re: [osv-dev] Problems with socat

2020-07-23 Thread Pekka Enberg
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