Since this is accepted, can we land this? There is a new upstream 0.9.4.

Any comments on this change?

In D55789#1276669, @jfree wrote:

In D55789#1276630, @markj wrote:

A bit tangential, but: we found a while back that it was possible to trivially livelock a core by scheduling timeouts of 1ns using EVFILT_TIMER or setitimer(). Basically, it takes longer than the callout interval to execute the callout handler, so the callout handler ends up running in a loop.

I should note that the current timerfd implementation fails to pass the timerfd__periodic_timer_performance test, which expects 400000000 individual nanosecond timeouts. I usually see 360000000 - 380000000 timeouts printed by the test case. I'm not sure if this performance issue is related to the core livelock in some way. The callout routine (timerfd_expire()) is fairly lightweight, specifying absolute expiration time with maximum precision (no C_PREL() or pr specified).

Isaac, let me know if you want to take over maintainership of this port for the long run. But if not, I'd be interested in keeping it going on the FreeBSD ports side.

Thanks! Also noticed that wireplumber needed an update, so sent the review out for that. I'll commit the two of them together.

Oops, fixed missing files/ncursesw.pc in v3.

You can just cat all these patches into a giant one and put it under files/, though.

@aokblast this commit breaks the following tests in CI:

How about this? I think keeping the static_cast instead is more consistent with the rest of this source file.

Fixed weird whitespace in v2

I think the convenience is nice for sure, but the flexibility of choice is reduced. If anything, maybe I can add a variable similar to FAILFILE that is configurable so that users can choose where it goes?

Thanks, abandoning this review in favour of D55800 and D55803 by the author then.

Superseded by 56ce17a57a84d3de205162ba1ad2a64bd91ae18a.

If PKG_CREATE_THREADS_NUMBER <= 0, it gets kern.smp.cores || nproc. But aren't -T0 and -T$(sysctl kern.smp.cores) expected to mean the same thing?

1. 0 is a perfectly valid value for -T, as your comment notes. But if that's what the user requests, it gets overwritten by...
2. kern.smp.cores, which should be identical to just doing -T0 but with an extra shell call.

Committed in D55634 with f26cb4757eb74ceace39144933ae198ebf1b4f28.

Sounds good, I'll commit mine and show the warning in the commit message.

Ah sorry, I accidentally submitted a review for a similar thing, but I think BUILD_BUG_ON(swap) is cleaner?

Duplicate of D55554.

It seems that the test added by this commit is failing in CI: https://ci.freebsd.org/job/FreeBSD-main-amd64-test/27898/testReport/sys.netlink/test_rtnl_gre/test_rtnl_gre/

Applied feedback, will commit this version.

I already have an update to an older development snapshot prepared and will work off that.

Thanks for the feedback. I like the plan of going ahead with emulators/rvvm-devel. I'd like to start using this in projects like Bricoler to speed up riscv64 CI and clean up failing tests, so tracking the latest improvements is important to me.

Cleaning out stale reviews.

Updated from discussion offline. I will commit this version instead. I will figure out a way to add "skip reason" metadata to Kyua in a future patch.

Added a comment pointing to the pkg origin of dhcpd

Thanks, will do. Abandoning this now then.

Closed by https://cgit.freebsd.org/ports/commit/?id=c4faf46ff4741f016c5196e1de77822733ff4a1f, I had linked the wrong review in the commit message, sorry about that!

Closed by https://cgit.freebsd.org/ports/commit/?id=919a4da7ff9794ffa53dbdd972ae25ec30368fa0, I had linked the wrong revision in the commit message so the automation didn't pick it up.