On 3/10/25 2:21 PM, Stephen Hemminger wrote:
On Tue, 4 Mar 2025 11:22:50 -0800
Patrick Mahan <ma...@mahan.org> wrote:
Morning,
This might be simple question, but it has my curiosity itching.
I did a quick scan through the documentation, but I did not see any good
guidelines for determining the number of HugeTLB based on the number of PMDs and
number of RX/TX queues.
I'm am looking at three different platforms, one has 2 ports (ixgbe), one has 3
ports (1 e1000 and 2 i40es) and a third has 2 ports (1 e1000 and 1 Cavium
liquidIO).
I'm trying to come up with some means of defining the HugeTLB requirements other
than trial and error.
Thanks,
Patrick
There is on exact way to estimate this. But for most applications the largest
memory footprint
is the mbuf pool. For sizing the mbuf pool you need to account for all the
NIC's, queues, and descriptor arrays
as well as any internal staging buffers.
That's what I thought, but I was hoping for some group wisdom here. I am trying
to construct the various startup (two are systemd and one is still sysvinit) to
try and calculate this based on, as you pointed out, the # of NICS, the # of
queues, etc. The code was already using HugeTLBs for other stuff (RiB/FiB,
database) that I had written code to calculate that information based on the # of
entries in the database, the maximum # of routes, etc at boot time to reserve.
The move to DPDK adds more complexity to this as we are looking at leveraging
more CPU cores, which may mean more queues, which means more packets, etc.
Right now I've done some, back of the envelope, calculations, but that is not a
way to dynamically approach this.
Anyways, thanks for responding...
Patick
