Does Click guarantee to module owners that only one thread of control inside their module will be active at any time? If not, then should memory shared by the control path (e.g., handlers used to set up state) and the datapath (e.g., code executed in Element::push()) be protected by Spinlocks? thanks, Mike