Re: [PATCH v6 0/2] Methodology change for hugepage configuration

2024-05-29 Thread Juraj Linkeš
On Wed, May 15, 2024 at 4:50 PM Nicholas Pratte wrote: > > >What's the difference between this version and v4? > > Version 5 was a response to your suggestions regarding the semantics > of the hugepage variable names as it relates to countable or > uncountable nouns. This patch, which was original

Re: [PATCH v6 0/2] Methodology change for hugepage configuration

2024-05-15 Thread Nicholas Pratte
>What's the difference between this version and v4? Version 5 was a response to your suggestions regarding the semantics of the hugepage variable names as it relates to countable or uncountable nouns. This patch, which was originally just a single patch, was expanded into a patch series since the

Re: [PATCH v6 0/2] Methodology change for hugepage configuration

2024-05-13 Thread Juraj Linkeš
What's the difference between this version and v4? On Tue, May 7, 2024 at 7:44 PM Nicholas Pratte wrote: > > In order to prevent accidental misconfiguration of hugepages at runtime, > the following changes are made to only allow for configuration of 2MB > hugepages within the DTS config.yaml. In

Re: [PATCH v6 0/2] Methodology change for hugepage configuration

2024-05-07 Thread Nicholas Pratte
Resending the patch and superseding the old one on patchwork. I accidentally sent this patch series through some kind of container instance. On Tue, May 7, 2024 at 1:44 PM Nicholas Pratte wrote: > > In order to prevent accidental misconfiguration of hugepages at runtime, > the following changes a

[PATCH v6 0/2] Methodology change for hugepage configuration

2024-05-07 Thread Nicholas Pratte
In order to prevent accidental misconfiguration of hugepages at runtime, the following changes are made to only allow for configuration of 2MB hugepages within the DTS config.yaml. In the previous implementation, a default hugepage size was selected via the size listed in /proc/meminfo. The problem

[PATCH v6 0/2] Methodology change for hugepage configuration

2024-05-07 Thread Nicholas Pratte
In order to prevent accidental misconfiguration of hugepages at runtime, the following changes are made to only allow for configuration of 2MB hugepages within the DTS config.yaml. In the previous implementation, a default hugepage size was selected via the size listed in /proc/meminfo. The problem