Date
1 - 2 of 2
Locked VNET Device Drivers; increased memory footprint for af_packet v3
|
Laszlo Király
Hello fellow VPP developers!
I experienced an increase in memory allocation related to af_packet v3.
VPP is built from source from git version: e416893a5. The AF_PACKET interface is created by the go bin-api call AfPacketCreateV3
(invoking af_packet_create_v3 api call in VPP).
The amount of memory assigned to an af_packet socket appears to be 135MB per af_packet socket. In VPP based on git version 45207e0fb2 the memory assigned to an af_packet socket was around 20MB.
Is this memory allocation increase intentional? If not is it a known issue? Any workaround or patch exist (if it is a bug and it was fixed)?
Thanks in advance,
Laszlo
|
|
|
|
Laszlo Király
Hi,
Excuse me for the misunderstanding. Most probably this is not an issue in VPP. In the mentioned 'previous version of vpp (git version 45207e0fb2) the af_packet_create_v2 api was used, so the memory increase is expected.
So, the question had lapsed.
/Laszlo
From: Laszlo Király
Sent: Tuesday, March 21, 2023 10:58 AM To: vpp-dev@... <vpp-dev@...> Subject: VNET Device Drivers; increased memory footprint for af_packet v3
Hello fellow VPP developers!
I experienced an increase in memory allocation related to af_packet v3.
VPP is built from source from git version: e416893a5. The AF_PACKET interface is created by the go bin-api call AfPacketCreateV3
(invoking af_packet_create_v3 api call in VPP).
The amount of memory assigned to an af_packet socket appears to be 135MB per af_packet socket. In VPP based on git version 45207e0fb2 the memory assigned to an af_packet socket was around 20MB.
Is this memory allocation increase intentional? If not is it a known issue? Any workaround or patch exist (if it is a bug and it was fixed)?
Thanks in advance,
Laszlo
|
|
|