Re: [L4s-discuss] L4S socket options

[rjmcmahon <[e-mail]>]

To clarify my question a bit. At the IETF 117 hackathon, I had to set 
both CCA's to prague for L4S to work properly. I originally only set the 
iperf client to prague and the iperf server ran reno. I was told they 
had to be set the same so I passed the client's CCA to the server as 
part of iperf's test exchange. So the server now starts and accepts() 
with reno (if no CCA is set on the server side) and after the connect 
will apply the CCA passed to it from the client, i.e. it's app level and 
not transport level exchange.

I didn't understand if this is required in future apps or if this was 
just something needed per the code level provided for the hackathon.

Bob
> Hi All,
> 
> Is there a set of socket options for L4S, specifically how can iperf 2
> enable & disable the low latency handling by the stack and network
> elements on an established flow? Currently, I've been assuming all
> prague CCAs will be treated as low latency and that's seemed to work.
> 
> I think I may be missing a setsockopt() option or two. Thanks for any
> clarifications here.
> 
> Bob
> 
> PS. Any pointers to relevant kernel header files are appreciated.