On 4/29/2022 3:03 PM, Stephen Hemminger wrote:
On Fri, 29 Apr 2022 14:52:03 -0400
Don Wallwork wrote:
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
> From: Don Wallwork [mailto:d...@xsightlabs.com]
> Sent: Friday, 29 April 2022 20.52
>
> 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,
On Fri, 29 Apr 2022 14:52:03 -0400
Don Wallwork wrote:
>
> 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
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 wrote:
On 4/26/2022 10:58 AM, Stephe
> >
> >> 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 is a good idea. Have you measured any performance differences
On 4/26/2022 8:42 PM, Honnappa Nagarahalli 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 is a good idea. Have you measu
+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 wrote:
> >
> >> On 4/26/2022 10:58 AM, Stephen Hemminger 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 is a good idea. Have you measured any performance differences with this
pa
On 4/26/2022 5:21 PM, Stephen Hemminger wrote:
On Tue, 26 Apr 2022 17:01:18 -0400
Don Wallwork wrote:
On 4/26/2022 10:58 AM, Stephen Hemminger wrote:
On Tue, 26 Apr 2022 08:19:59 -0400
Don Wallwork wrote:
Add support for using hugepages for worker lcore stack memory. The
intent is to
On Tue, 26 Apr 2022 17:01:18 -0400
Don Wallwork wrote:
> On 4/26/2022 10:58 AM, Stephen Hemminger wrote:
> > On Tue, 26 Apr 2022 08:19:59 -0400
> > Don Wallwork wrote:
> >
> >> Add support for using hugepages for worker lcore stack memory. The
> >> intent is to improve performance by reducing
On 4/26/2022 10:58 AM, Stephen Hemminger wrote:
On Tue, 26 Apr 2022 08:19:59 -0400
Don Wallwork 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
On Tue, 26 Apr 2022 08:19:59 -0400
Don Wallwork 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.
>
> Platforms desiring to m
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.
Platforms desiring to make use of this capability must enable the
associated option flag a
13 matches
Mail list logo
