> The work-in-progress design specification for "Pluggable TCP & SCTP > Congestion Control" is now available at: > > http://hub.opensolaris.org/bin/download/Project+npp/WebHome/cong-design.pdf
Looks great to me. A few questions/remarks: 3.4. The additional fields for the result of SCTP_GET_PEER_ADDR_INFO are only a small subset of the information in tcp_info, although one could see almost all the fields in tcp_info being equally applicable to SCTP. Wouldn't it make sense to just add the entire set? 4. Security Considerations: I'm fine with the current proposal to let all processes use all congestion control algorithms that are loaded in the system. You say that "ipadm remove-cong" is a big hammer if one want to restrict algorithm - that's true because it's system-wide. It would be nicer if it could be done in a zone-wide manner, but I guess there is no mechanism for restricting the visibility of such loaded modules to specific zones. 6.3. I'm not sure it's true that cwnd transition events are only of interest to kernel developers, testers, and congestion control researchers. I could see this information being used by performance engineers trying to understand throughput issues, correlating packet traces with events. So if a user-friendly dtrace interface could be found for this, that might be nice. (I have the impression that dtrace could be very useful for this kind of work, although I haven't got around to learning enough of it yet. :-) I can't comment on the kernel-internal interfaces, because that's also an area that I just don't know enough about. -- Simon. -- This message posted from opensolaris.org _______________________________________________ networking-discuss mailing list networking-discuss@opensolaris.org
