Here is the curated list of bug fixes from Spirent fork (this list and another below do not include most of the IPV6 code on ipv6 branch, nor the commits that have been already merged into OSv master, nor recent patches I have submitted to implement netlink and fix getifaddrs, if_nameindex, if_nametoindex and if_indextoname):
pthread: add simplisitic {get,set}schedparam - this looks better and possibly more functional than what we have now which I added with this commit d39860d11; on other hand the Spirent version seems to assume the default policy as SCHED_RR which I am not sure is correct
hypervisor "steal" time driver for KVM and VMware; as above came in the form of many commits but the "steal" time functionality does not seem to be plugged in anywhere so possibly unfinished?
XEN: backport FreeBSD Xen 4.2.1 and related patches; assessing and testing it requires some XEN experience and necessary setup; also considering the latest release of XEN is 4.15, is it worth porting these patches?
Here is the curated list of bug fixes from Spirent fork (this list and another below do not include most of the IPV6 code on ipv6 branch, nor the commits that have been already merged into OSv master, nor recent patches I have submitted to implement netlink and fix getifaddrs, if_nameindex, if_nametoindex and if_indextoname):
Don't leak directory entries when processing the init entries - no brainer(has been merged)pthread_getname_np()
on master now but possibly can improve error handling like in the Spirent forktcp_input.cc: Fix a race condition on tcp listen socket teardown
tcp_input.cc: Fix a race condition on tcp listen socket teardown
My sense is that some or possibly all network stack fixes from the list above are on the ipv6 branch of the main repo.
Here is the curated list of enhancements from Spirent fork that map to one or more commits:
syscalls: allocate local iovec copies on the stack instead of the heap - this seems a no brainer but not have a clue how much difference does it really make(has been merged)virtio-blk: Use multiplex strategy for I/O(has been merged)Handle case if we're send to our non-loopback address and a cache entry gets added for it- fixed by a0251df210a6739830bd37e52211268f5672a27c