lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1494430466.29205.17.camel@redhat.com>
Date:   Wed, 10 May 2017 11:34:26 -0400
From:   Rik van Riel <riel@...hat.com>
To:     Marcelo Tosatti <mtosatti@...hat.com>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Cc:     Luiz Capitulino <lcapitulino@...hat.com>,
        Linux RT Users <linux-rt-users@...r.kernel.org>
Subject: Re: [patch 3/3] MM: allow per-cpu vmstat_worker configuration

On Wed, 2017-05-03 at 15:40 -0300, Marcelo Tosatti wrote:
> Following the reasoning on the last patch in the series,
> this patch allows configuration of the per-CPU vmstat worker:
> it allows the user to disable the per-CPU vmstat worker.
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@...hat.com>

Is there ever a case where you would want to configure
this separately from the vmstat_threshold parameter?

What use cases are you trying to address?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ