devel/magit: Update to 4.7.0
- Track upstream's replacement of docs/RelNotes/ with
per-major-release docs/CHANGELOG.N files in PORTDOCS and the DOCS
install
- Fix the DOCS and PDF options. With the custom do-build target,
DOCS_ALL_TARGET/PDF_ALL_TARGET never ran, so the HTML and PDF
manuals were never built and staging failed. Build them explicitly
in post-build-DOCS-on/post-build-PDF-on, under MAKE_ENV so the
sed=gsed binary alias is on PATH.
Changelog: https://github.com/magit/magit/blob/v4.7.0/docs/CHANGELOG.4#v470----2026-08-01
Sponsored by: The FreeBSD Foundation
misc/lbann: update 0.102-254 → 0.104
PR: 295214
Submitted by: Chad Jacob Milios <milios at ccsys.com> (initial version, additional changes were made on top of his patch to make it build)
misc/emacs-libvterm: Install etc/ under the vterm/
Previously, the shell-integration scripts (emacs-vterm-bash.sh,
emacs-vterm-zsh.sh, emacs-vterm.fish) were installed under
${EMACS_SITE_LISPDIR}/etc/, i.e. share/emacs/site-lisp/etc/. That is a
shared, generically-named directory, and creating it cause problems for
at least one other package [0].
Install everything under ${EMACS_SITE_LISPDIR}/vterm/ instead. This
keeps the port self-contained, no longer pollutes a directory other
ports probe, and matches ELPA package's layout.
[0]
math/ess auto-detects ess-etc-directory by probing paths relative to its
own lisp directory, one of which is ../etc. With site-lisp/etc present,
ESS selected it instead of the correct share/emacs/etc/ess, so M-x R
failed to load ESSR with "cannot open the connection".
Approved by: maintainer timeout
[2 lines not shown]
ena: Update driver version to v2.8.4
Bug Fixes:
* Fix false 'missing TX completions' warnings due to timestamp race
* Put taskqueues into correct NUMA domain if !RSS
Minor Changes:
* Batch RX statistics updates
* Swap RX/TX completions cleanup order
Submitted by: Arthur Kiyanovski <akiyano at amazon.com>
MFC after: 2 weeks
Sponsored by: Amazon, Inc.
Reviewed by: cperciva
Differential Revision: https://reviews.freebsd.org/D58242
(cherry picked from commit 605e699cd6ca4feae6c73c5c5ea8337054897116)
ena: Fix false 'missing TX completions' warnings due to timestamp race
Sporadic 'Found a Tx that wasn't completed on time' warnings appear
under sustained TX load, always reporting '1 msecs since last cleanup'
despite the 5-second timeout threshold.
The per-packet TX timestamp uses struct bintime (128 bits: two 64-bit
fields sec and frac) which is read and written non-atomically. A race
exists between the missing TX completion check
(check_missing_comp_in_tx_queue reading the timestamp) and the TX
submit path or cleanup path writing it on another CPU. Since the two
fields are not updated atomically, the check can observe a partially
written timestamp - one field from the old value and one from the new.
This can produce a timestamp with {sec=0, frac=valid}, causing the
check to compute a time offset equal to system uptime and falsely
exceeding the 5-second timeout.
Confirmed by instrumentation showing all occurrences had sec=0 with
valid frac/mbuf, cleanup_running=0, and ticks==last_cleanup_ticks.
[24 lines not shown]
ena: Batch RX statistics updates
Move per-packet counter_enter/counter_exit pairs out of the RX
processing loop and batch them into a single update after the
loop completes.
Previously, each received packet triggered two separate
counter_enter/counter_exit blocks -- one for bytes and one for
packet count. This commit accumulates totals in local variables
and updates all four counters (ring and hw stats for both packets
and bytes) in a single counter_enter/counter_exit block after the
loop.
Also move the stats update to after the refill and LRO flush
so that the error path (goto update_stats) and the normal path
converge at the same label, avoiding code duplication.
Submitted by: David Arinzon <darinzon at amazon.com>
MFC after: 2 weeks
[5 lines not shown]
ena: Swap cleanup order
As RX processing is heavier than TX completions processing, swap the
order and process TX completions first, in order to avoid starving the
completions and causing potential missing TX completions.
Submitted by: Ofir Tabachnik <ofirt at amazon.com>
MFC after: 2 weeks
Sponsored by: Amazon, Inc.
Reviewed by: cperciva
Differential Revision: https://reviews.freebsd.org/D58239
(cherry picked from commit f08def9ed97f45700eb0611a3fd9240210c9303e)
