On Fri, Apr 28, 2023 at 11:00:43AM -0600, Philip Prindeville wrote: > My own experience disagrees. > > I spent 17 months bringing up a Xeon-D based traffic shaper for 40Gb/s of > traffic in a radio base station. > > And yes, when collected crunched traffic statistics, it did use more than 4GB > of address space to do so.
I can believe that. Though I kind of doubt this is the typical usage of OpenWRT. A kernel can have both amd64 and x32 enabled. My thinking was in typical usage most programs won't be that large and thus x32 is smaller and faster. Note, enabling CONFIG_X86_X32 does not force the use of x32 userspace, it merely allows it. The observed kernel runtime was 4KB larger which translates to +1-8191 bytes. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445 _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
