On Tue, Jan 20, 2015 at 09:51:26AM +0200, Konstantin Belousov wrote:
K> > Like stated in the manual page, callout_reset_curcpu/on() does not work
K> > with MPSAFE callouts any more!
K> I.e. you 'fixed' some undeterminate bugs in callout migration by not
K> doing migration at all anymore.
K>
K> >
K> > You need to use callout_init_{mtx,rm,rw} and remove the custom locking
K> > inside the callback in the TCP stack to get it working like before!
K>
K> No, you need to do this, if you think that whole callout KPI must be
K> rototiled. It is up to the person who modifies the KPI, to ensure that
K> existing code is not broken.
K>
K> As I understand, currently we are back to the one-cpu callouts.
K> Do other people consider this situation acceptable ?
I think this isn't acceptable. The commit to a complex subsystem
lacked a review from persons involved in the system before. The
commit to subsystem broke consumers of the subsystem and this
was even done not accidentially, but due to Hans not caring about
it.
As for me this is enough to request a backout, and let the change
back in only after proper review.
--
Totus tuus, Glebius.
_______________________________________________
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
