linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Christoph Lameter <cl@linux.com>,
	linux-mm@kvack.org, ghaskins@londonstockexchange.com,
	niv@us.ibm.com, kravetz@us.ibm.com,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: vmstat kthreads
Date: Wed, 19 Jun 2013 07:59:07 -0700	[thread overview]
Message-ID: <20130619145906.GB5146@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOtvUMc5w3zNe8ed6qX0OOM__3F_hOTqvFa1AkdXF0PHvzGZqg@mail.gmail.com>

On Wed, Jun 19, 2013 at 05:50:46PM +0300, Gilad Ben-Yossef wrote:
> On Wed, Jun 19, 2013 at 5:23 PM, Christoph Lameter <cl@linux.com> wrote:
> > On Tue, 18 Jun 2013, Paul E. McKenney wrote:
> >
> >> > Gilad Ben-Yossef has been posting patches that address this issue in Feb
> >> > 2012. Ccing him. Can we see your latest work, Gilead?
> >>
> >> Is it this one?
> >>
> >> https://lkml.org/lkml/2012/5/3/269
> >
> > Yes that is it. Maybe the scheme there could be generalized so that other
> > subsystems can also use this to disable their threads if nothing is going
> > on? Or integrate the monitoring into the notick logic somehow?
> >
> 
> I respinned the original patch based on feedback from Christoph for
> 3.2 and even did some light testing then, but got distracted and never
> posted the result.
> 
> I've just ported them over to 3.10 and they merge (with a small fix
> due to deferred workqueue API changes) and build. I did not try to run
> this version though.
> I'll post them as replies to this message.
> 
> I'd be happy to rescue them from the "TODO" pile... :-)

Please!  ;-)

							Thanx, Paul

--
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>

  parent reply	other threads:[~2013-06-19 15:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 15:23 Paul E. McKenney
2013-06-18 17:46 ` Christoph Lameter
2013-06-18 18:26   ` Paul E. McKenney
2013-06-19 14:23     ` Christoph Lameter
2013-06-19 14:50       ` Gilad Ben-Yossef
2013-06-19 14:57         ` Gilad Ben-Yossef
2013-06-20  5:06           ` Gilad Ben-Yossef
2013-06-19 14:59         ` Paul E. McKenney [this message]
2013-06-19 20:18           ` Christoph Lameter
2013-06-19 20:02         ` [PATCH v2 1/2] mm: make vmstat_update periodic run conditional Gilad Ben-Yossef
2013-06-20 14:05           ` Christoph Lameter
2013-08-07 18:16             ` Christoph Lameter
2013-08-08  6:28               ` Gilad Ben-Yossef
2013-08-08  6:54             ` Gilad Ben-Yossef
2013-08-08 14:59               ` Christoph Lameter
2013-08-09 18:56                 ` Gilad Ben-Yossef
2013-08-28 19:28                   ` Christoph Lameter
2013-06-19 20:02         ` [PATCH v2 2/2] mm: add sysctl to pick vmstat monitor cpu Gilad Ben-Yossef
2013-06-20 13:58           ` Christoph Lameter

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=20130619145906.GB5146@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=cl@linux.com \
    --cc=fweisbec@gmail.com \
    --cc=ghaskins@londonstockexchange.com \
    --cc=gilad@benyossef.com \
    --cc=kravetz@us.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=niv@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox