Martin Pieuchot <m...@openbsd.org> writes: > On 11/10/17(Wed) 17:01, Martin Pieuchot wrote: >> OpenBSD 6.2 includes nice performance and latency improvements due to >> the work done in the Network Stack in the previous years. However as >> soon as IPsec is enabled, all network related processing are affected. >> In other words you cannot profit from the last MP work in the Network >> stack if you use IPsec.
By "IPsec is enabled," do you mean as soon as an AS appears in the kernel? Or is it some other condition? >> During the last 6 months I hoped that somebody else would look at the >> IPsec stack and tell us what needs to be done. This didn't happen. >> >> Now that 6.2 is released, we cannot afford to continue to parallelize >> the Network Stack if some of our users and testers still run it under >> KERNEL_LOCK(). >> >> So I did an audit of the IPsec stack and came with the small diff below. >> This diff doesn't remove the KERNEL_LOCK() (yet), but add some asserts >> to make sure that the global data structure are all accessed while >> holding the NET_LOCK(). > > Here's the diff to stop grabbing the KERNEL_LOCK(), please test and > report back. I have several iked tunnels that are normally active. I applied both patches last night against 6.2-stable, rebooted, and my router was hung when I woke up this morning. Unfortunately I wasn't really set up to capture crash information, and there are no dumps in /var/crash/. I don't have much experience with capturing OpenBSD kernel panics. I've set up screen on another system so that I'll have a log of serial console activity (this is an apu2c4) and have set ddb.console=1. I will also reboot with bsd.gdb this time. Is there anything else I should to increase my chances of getting a useful dump? -TimS -- Tim Stewart ----------- Mail: t...@stoo.org Matrix: @tim:stoo.org
