seladb
seladb
@Dimi1010 is correct - there is actually one RX ring between the user space and the kernel space. `rxId` is the slot inside the ring and not the rx queue...
@Dimi1010 @JasMetzger I think you're right! We can definitely support setting the hardware RX queue. I'd start with adding it to `XdpDeviceConfiguration` so users can configure it. I'd also check...
If we want to have one `XdpDevice` / socket per queue - I think it'd make sense to add it to `XdpDeviceConfiguration` since it'd be a config param of the...
> It seems the headroom should be part of the configuration too. Currently it defaults to zero. Is this something that can be added to the PR used for rx...
> OK--thanks. It will be along the same lines as the rx queue id. Yes, that'd be great 👍
@matthiasklein thanks for the detailed explanation of your scenarios. To be honest, I'm not super familiar with FTP servers and how they work, and I'm not a TCP protocol expert...
@matthiasklein the `X509Toolkit` tests fail, I assume that this change is related. Can you please take a look?
@matthiasklein can you please walk me through this fix? Here is what I'm trying to understand: if a FIN packet has the expected sequence number, we still close the connection...
@matthiasklein thanks, I think I understand this solution. Why not treat RST packets the same? Also - do you have a pcap that you can add that tests this scenario?
@matthiasklein this pcap file contains 2 flows - I believe the one that is sending a FIN packet out-of-order is the one with 117 packets, and the early FIN is...