Could probably get an SPDX tag.

Even with the other locks it won't give us want we want. I assume it's likely okay to accept the race as otherwise we'd probably have to sort this out in the native PCI layer? @jhb?

How does that lock prevent us from any other changes at the same time by anything calling pcie_capability_write_word() in between?

There is just no maxdgram limit at all, AFAIU. And we should do
the same unless anybody has good explanation for such a limit.

As suggested by @jhb:

• use mp_ncpus and CPU_FOREACH which will account for absent CPUs.
• use global static rather than using [0] to free the 2nd allocation

In D42830#976902, @glebius wrote:

In D42830#976836, @bz wrote:

Yes, but it worked for almost 40 years and on every other UNIX/Linux does too. [..] The limits put into that file in the last millennium were and are really not adequate anymore in the last 20 years (despite never been enforced anyway).
Also the changes broke the previous syslogd fixes; this is not just wpa.

Linux doesn't have maximum datagram size limit at all. On Linux SO_SNDBUF really controls socket buffer size, just like it does on FreeBSD 14. Btw, their default buffer size is huge over 200k. Linux also has a limit for how many datagrams are queued, which makes some sense.

Address some comments from @jhb; wait for clarification on the last one.