On 4/27/2022 4:17 AM, Morten Brørup wrote:
+CC: EAL and Memory maintainers.
From: Don Wallwork [mailto:d...@xsightlabs.com]
Sent: Tuesday, 26 April 2022 23.26
On 4/26/2022 5:21 PM, Stephen Hemminger wrote:
On Tue, 26 Apr 2022 17:01:18 -0400
Don Wallwork <d...@xsightlabs.com> wrote:
On 4/26/2022 10:58 AM, Stephen Hemminger wrote:
On Tue, 26 Apr 2022 08:19:59 -0400
Don Wallwork <d...@xsightlabs.com> wrote:
Add support for using hugepages for worker lcore stack memory. The intent is to
improve performance by reducing stack memory related TLB misses and also by
using memory local to the NUMA node of each lcore.
This certainly seems like a good idea!
However, I wonder: Does the O/S assign memory local to the NUMA node to an
lcore-pinned thread's stack when instantiating the tread? And does the DPDK EAL
ensure that the preconditions for the O/S to do that are present?
(Not relevant for this patch, but the same locality questions come to mind
regarding Thread Local Storage.)
Currently, DPDK does not set pthread affinity until after the pthread is
created and the stack has been allocated. If the affinity attribute
were set before the pthread_create call, it seems possible that
pthread_create could be NUMA aware when allocating the stack. However,
it looks like at least the glibc v2.35 implementation of pthread_create
does not consider this at stack allocation time.
Platforms desiring to make use of this capability must enable the
associated option flag and stack size settings in platform config
files.
---
lib/eal/linux/eal.c | 39
+++++++++++++++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
Good idea but having a fixed size stack makes writing complex application more
difficult. Plus you lose the safety of guard pages.
Would it be possible to add a guard page or guard region by using the O/S
memory allocator instead of rte_zmalloc_socket()? Since the stack is considered
private to the process, i.e. not accessible from other processes, this patch
does not need to provide remote access to stack memory from secondary processes
- and thus it is not a requirement for this features to use DPDK managed memory.
In order for each stack to have guard page protection, this would likely
require reserving an entire hugepage per stack. Although guard pages do
not require physical memory allocation, it would not be possible for
multiple stacks to share a hugepage and also have per stack guard page
protection.
Thanks for the quick reply.
The expectation is that use of this optional feature would be limited to cases
where the performance gains justify the implications of these tradeoffs. For
example, a specific data plane application may be okay with limited stack size
and could be tested to ensure stack usage remains within limits.
How to identify the required stack size and verify it... If aiming for small
stacks, some instrumentation would be nice, like rte_mempool_audit() and
rte_mempool_list_dump().
Theoretically, a region of memory following the stack could be populated
with a poison pattern that could be audited. Not as robust as hw
mprotect/MMU, but it could provide some protection.
Alternatively, just assume that the stack is "always big enough", and don't
worry about it - like the default O/S stack size. And as Stephen already mentioned:
Regardless of stack size, overflowing the stack will cause memory corruption instead of a
segmentation fault.
Keep in mind that the required stack size not only depends on the application,
but also on DPDK and other libraries being used by the application.
Also, since this applies only to worker threads, the main thread would not be
impacted by this change.
I would prefer it as a runtime, not compile time option.
That way distributions could ship DPDK and application could opt in if it
wanted.
Good point.. I'll work on a v2 and will post that when it's ready.
May I suggest using the stack size configured in the O/S, from
pthread_attr_getstacksize() or similar, instead of choosing the stack size
manually? If you want it to be configurable, use the default size unless
explicitly specified otherwise.
Yes, that can be handled in EAL args. I'll include that in the next
version.
Do the worker threads need a different stack size than the main thread? In my opinion: "Nice
to have", not "must have".
The main thread stack behaves differently anyway; it can grow
dynamically, but regarless of this patch, pthread stack sizes are always
fixed. This change only relates to worker threads.
Do the worker threads need different stack sizes individually? In my opinion: Perhaps "nice to
have", certainly not "must have".
Currently, worker thread stack sizes are uniformly sized and not
dynamically resized. This patch does not change that aspect. Given
that, it seems unnecessary to add that complexity here.
