On Tue, May 09, 2017 at 05:54:33PM +0000, Bart Van Assche wrote: > > * Bonus points: consolidate the srp daemon. Debian ships a different > > service file than upstream, but I am against an additional layer > > introduced by srp_daemon.sh. It would also be nice to have a systemd > > service shipped by upstream (and not just in the redhat directory) > > I will have a look at this too. My thoughts.. It looked to me like srp_daemon needed one process per port. The best path looked to me like using systemd templates (eg srp_daemon@mlx4_0/0) to allow systemd to directly manage the per port srp_daemon. Then the question is how to request the right templates are created.. Perhaps udev rules can do this directly, but I'm not sure about how to get the port #, perhaps an udev triggered script or something can do it. Perhaps there could be an inbetween progarm that took the udev events and asked systemd to make the right units. Another option is to have a srp_daemon 'runner' that monitors udev and actively manages a set of fork'd childern so that the children cover all required ports. But this is actually somewhat hard to do well.. The big issue with the redhat script is that it is not hotplug safe, and needs special boot ordering, which we really need to get away from in general for robustness. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
