From: Rik van Riel <riel@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: [patch 3/3] MM: allow per-cpu vmstat_worker configuration
Date: Wed, 10 May 2017 11:34:26 -0400 [thread overview]
Message-ID: <1494430466.29205.17.camel@redhat.com> (raw)
In-Reply-To: <20170503184039.901336380@redhat.com>
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@redhat.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?
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: [patch 3/3] MM: allow per-cpu vmstat_worker configuration
Date: Wed, 10 May 2017 11:34:26 -0400 [thread overview]
Message-ID: <1494430466.29205.17.camel@redhat.com> (raw)
In-Reply-To: <20170503184039.901336380@redhat.com>
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@redhat.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?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-10 15:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 18:40 [patch 0/3] per-CPU vmstat thresholds and vmstat worker disablement (v2) Marcelo Tosatti
2017-05-03 18:40 ` Marcelo Tosatti
2017-05-03 18:40 ` [patch 1/3] MM: remove unused quiet_vmstat function Marcelo Tosatti
2017-05-03 18:40 ` Marcelo Tosatti
2017-05-10 13:36 ` Rik van Riel
2017-05-10 13:36 ` Rik van Riel
2017-05-03 18:40 ` [patch 2/3] MM: allow per-cpu vmstat_threshold configuration Marcelo Tosatti
2017-05-03 18:40 ` Marcelo Tosatti
2017-05-03 18:40 ` [patch 3/3] MM: allow per-cpu vmstat_worker configuration Marcelo Tosatti
2017-05-03 18:40 ` Marcelo Tosatti
2017-05-10 15:34 ` Rik van Riel [this message]
2017-05-10 15:34 ` Rik van Riel
2017-05-11 15:33 ` Marcelo Tosatti
2017-05-11 15:33 ` Marcelo Tosatti
2017-05-16 1:31 ` [lkp-robot] [MM] 3e38a07a66: ltp.proc01.fail kernel test robot
2017-05-16 1:31 ` kernel test robot
2017-05-16 1:31 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1494430466.29205.17.camel@redhat.com \
--to=riel@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.