Matthew Chapman

``` return cycles * NANOS_PER_SEC / exanic->tick_hz; ``` I don't think this will work, `cycles * NANOS_PER_SEC` will overflow. I agree that there might be some optimisations possible though... the...

It does vary, e.g.: ExaNIC X2/X4/X10/X40/FDK 1.x: 161Mhz ExaNIC V5P/FDK 2.x/future cards: 322Mhz ExaNIC GM: 250Mhz ExaNIC HPT: 4Ghz There may be a way to optimise the arithmetic a bit,...

Re: ``` $ ./a.out 541 192.168.1.50 8000 Connected to 192.168.1.50:8000 exasock_tcp_get_device: Operation not supported ``` You need to run `exasock ./a.out 541 192.168.1.50 8000`. Linking with -lexasock_ext just provides the...

Hi Tudor, Thanks for the very detailed analysis here and in separate emails, bits of which I've seen via various channels. To answer your questions about PCIe - ExaNICs send...

You can use IPv6 with ExaNICs through the normal kernel stack, but the exasock acceleration stack only supports IPv4. There are no plans to support IPv6 in exasock, honestly I've...

Thank you for the pull request, we are looking at it. Can you comment on what happens when you run this with multiple namespaces? Our concern is that it does...