Replace all post_url with Hugo ref blocks

content/articles/2024-02-17-vpp-freebsd-2.md

@@ -28,7 +28,7 @@ over 2023 and forward to 2024:
 > experience, improving hardware support on arm64 platforms, and adding support for low power idle
 > on Intel and arm64 hardware.
 
-In my first [[article]({% post_url 2024-02-10-vpp-freebsd-1 %})], I wrote a sort of a _hello world_
+In my first [[article]({{< ref "2024-02-10-vpp-freebsd-1" >}})], I wrote a sort of a _hello world_
 by installing FreeBSD 14.0-RELEASE on both a VM and a bare metal Supermicro, and showed that Tom's
 VPP branch compiles, runs and pings. In this article, I'll take a look at some comparative
 performance numbers.
@@ -41,7 +41,7 @@ utilities like a _netmap_ bridge, and of course completely userspace based datap
 VPP project that I'm working on here. Last week, I learned that VPP has a _netmap_ driver, and from
 previous travels I am already quite familiar with its _DPDK_ based forwarding. I decide to do a
 baseline loadtest for each of these on the Supermicro Xeon-D1518 that I installed last week. See the
-[[article]({% post_url 2024-02-10-vpp-freebsd-1 %})] for details on the setup.
+[[article]({{< ref "2024-02-10-vpp-freebsd-1" >}})] for details on the setup.
 
 The loadtests will use a common set of different configurations, using Cisco T-Rex's default
 benchmark profile called `bench.py`:
@@ -203,7 +203,7 @@ the kernel (which clocked in at 1.2Mpps).
 It's good to have a baseline on this machine on how the FreeBSD kernel itself performs. But of
 course this series is about Vector Packet Processing, so I now turn my attention to the VPP branch
 that Tom shared with me. I wrote a bunch of details about the VM and bare metal install in my
-[[first article]({% post_url 2024-02-10-vpp-freebsd-1 %})] so I'll just go straight to the
+[[first article]({{< ref "2024-02-10-vpp-freebsd-1" >}})] so I'll just go straight to the
 configuration parts:
 
 ```