Scheffenegger, Richard <richard.scheffeneg...@netapp.com> wrote: >Sorry, I though this was a problem on stable/13. > >This is only in HEAD, stable/13 and 13.0 - never MFC'd to stable/12 or >backported to >12.1 > >> I did some reshuffling of socket-upcalls recently in the TCP stack, to >> prevent some race conditions with our $work in-kernel NFS server >> implementation. The FreeBSD krpc/nfs definitely uses upcalls. On the server side the upcall just "activates" a thread to service the socket (soreceive() etc). The client side upcall does quite a bit more, including soreceive(). Timing shouldn't be a problem, so long as upcalls happen when there is data to be received or the socket has been closed at the other end. I test with pretty current sources and haven't seen issues. If I do see problems, I'll be sure to let you know.;-)
rick Are these changes in 12.1p5? This is the OS version used by the reporter of the bug. Best regards Michael _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
