Sven-Haegar Koch wrote:
> On Tue, 25 Feb 2014, Dave Hansen wrote:
>
>
>> On 02/25/2014 03:09 PM, Alexander Graf wrote:
>>
Couldn't we also (maybe in parallel) just teach the sysctl userspace
about sysfs? This way we don't have to do parallel sysctls and sysfs
for *EVERYTHING
On Tue, 25 Feb 2014, Dave Hansen wrote:
> On 02/25/2014 03:09 PM, Alexander Graf wrote:
> >> Couldn't we also (maybe in parallel) just teach the sysctl userspace
> >> about sysfs? This way we don't have to do parallel sysctls and sysfs
> >> for *EVERYTHING* in the kernel:
> >>
> >>sysfs.kerne
> Am 26.02.2014 um 09:05 schrieb Hugh Dickins :
>
>> On Tue, 25 Feb 2014, Johannes Weiner wrote:
>>> On Tue, Feb 25, 2014 at 12:28:04AM +0100, Alexander Graf wrote:
>>> Configuration of tunables and Linux virtual memory settings has
>>> traditionally
>>> happened via sysctl. Thanks to that ther
On Tue, 25 Feb 2014, Johannes Weiner wrote:
> On Tue, Feb 25, 2014 at 12:28:04AM +0100, Alexander Graf wrote:
> > Configuration of tunables and Linux virtual memory settings has
> > traditionally
> > happened via sysctl. Thanks to that there are well established ways to make
> > sysctl configurati
On 02/25/2014 03:09 PM, Alexander Graf wrote:
>> Couldn't we also (maybe in parallel) just teach the sysctl userspace
>> about sysfs? This way we don't have to do parallel sysctls and sysfs
>> for *EVERYTHING* in the kernel:
>>
>>sysfs.kernel.mm.transparent_hugepage.enabled=enabled
>
> It's p
On Tue, Feb 25, 2014 at 6:34 PM, Dave Hansen wrote:
> On 02/24/2014 03:28 PM, Alexander Graf wrote:
>> Configuration of tunables and Linux virtual memory settings has traditionally
>> happened via sysctl. Thanks to that there are well established ways to make
>> sysctl configuration bits persisten
On Wed, Feb 26, 2014 at 12:16 AM, Alexander Graf wrote:
>
>
>>> Am 26.02.2014 um 01:19 schrieb Peter Zijlstra :
>>>
On Tue, Feb 25, 2014 at 12:15:28PM -0500, Johannes Weiner wrote:
On Tue, Feb 25, 2014 at 12:28:04AM +0100, Alexander Graf wrote:
Configuration of tunables and Linux vi
>> Am 26.02.2014 um 01:19 schrieb Peter Zijlstra :
>>
>>> On Tue, Feb 25, 2014 at 12:15:28PM -0500, Johannes Weiner wrote:
>>> On Tue, Feb 25, 2014 at 12:28:04AM +0100, Alexander Graf wrote:
>>> Configuration of tunables and Linux virtual memory settings has
>>> traditionally
>>> happened via s
> Am 26.02.2014 um 01:34 schrieb Dave Hansen :
>
>> On 02/24/2014 03:28 PM, Alexander Graf wrote:
>> Configuration of tunables and Linux virtual memory settings has traditionally
>> happened via sysctl. Thanks to that there are well established ways to make
>> sysctl configuration bits persisten
On 02/24/2014 03:28 PM, Alexander Graf wrote:
> Configuration of tunables and Linux virtual memory settings has traditionally
> happened via sysctl. Thanks to that there are well established ways to make
> sysctl configuration bits persistent (sysctl.conf).
>
> KSM introduced a sysfs based configu
On Tue, Feb 25, 2014 at 12:15:28PM -0500, Johannes Weiner wrote:
> On Tue, Feb 25, 2014 at 12:28:04AM +0100, Alexander Graf wrote:
> > Configuration of tunables and Linux virtual memory settings has
> > traditionally
> > happened via sysctl. Thanks to that there are well established ways to make
>
On Tue, Feb 25, 2014 at 12:28:04AM +0100, Alexander Graf wrote:
> Configuration of tunables and Linux virtual memory settings has traditionally
> happened via sysctl. Thanks to that there are well established ways to make
> sysctl configuration bits persistent (sysctl.conf).
>
> KSM introduced a s
On 02/24/2014 06:28 PM, Alexander Graf wrote:
> Configuration of tunables and Linux virtual memory settings has traditionally
> happened via sysctl. Thanks to that there are well established ways to make
> sysctl configuration bits persistent (sysctl.conf).
>
> KSM introduced a sysfs based configu
13 matches
Mail list logo
