All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: cl@linux.com, akpm@linux-foundation.org, mhocko@kernel.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, hannes@cmpxchg.org,
	mgorman@suse.de
Subject: Re: [patch 3/3] vmstat: Create our own workqueue
Date: Thu, 29 Oct 2015 12:08:22 +0900	[thread overview]
Message-ID: <20151029030822.GD27115@mtj.duckdns.org> (raw)
In-Reply-To: <20151029022447.GB27115@mtj.duckdns.org>

On Thu, Oct 29, 2015 at 11:24:47AM +0900, Tejun Heo wrote:
> Hello,
> 
> That's weird.
> 
> On Wed, Oct 28, 2015 at 08:57:28PM +0900, Tetsuo Handa wrote:
> > [  272.851035] Showing busy workqueues and worker pools:
> > [  272.852583] workqueue events: flags=0x0
> > [  272.853942]   pwq 6: cpus=3 node=0 flags=0x0 nice=0 active=1/256
> > [  272.855781]     pending: vmw_fb_dirty_flush [vmwgfx]
> > [  272.857500]   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
> > [  272.859359]     pending: vmpressure_work_fn
> > [  272.860840] workqueue events_freezable_power_: flags=0x84
> > [  272.862461]   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256
> > [  272.864479]     in-flight: 11286:disk_events_workfn
> 
> What's this guy doing?  Can you get stack dump on 11286 (or whatever
> is in flight in the next lockup)?

Wait, this series doesn't include Tetsuo's change.  Of course it won't
fix the deadlock problem.  What's necessary is Tetsuo's patch +
WQ_MEM_RECLAIM.

Thanks.

-- 
tejun

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

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <htejun@gmail.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: cl@linux.com, akpm@linux-foundation.org, mhocko@kernel.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, hannes@cmpxchg.org,
	mgorman@suse.de
Subject: Re: [patch 3/3] vmstat: Create our own workqueue
Date: Thu, 29 Oct 2015 12:08:22 +0900	[thread overview]
Message-ID: <20151029030822.GD27115@mtj.duckdns.org> (raw)
In-Reply-To: <20151029022447.GB27115@mtj.duckdns.org>

On Thu, Oct 29, 2015 at 11:24:47AM +0900, Tejun Heo wrote:
> Hello,
> 
> That's weird.
> 
> On Wed, Oct 28, 2015 at 08:57:28PM +0900, Tetsuo Handa wrote:
> > [  272.851035] Showing busy workqueues and worker pools:
> > [  272.852583] workqueue events: flags=0x0
> > [  272.853942]   pwq 6: cpus=3 node=0 flags=0x0 nice=0 active=1/256
> > [  272.855781]     pending: vmw_fb_dirty_flush [vmwgfx]
> > [  272.857500]   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
> > [  272.859359]     pending: vmpressure_work_fn
> > [  272.860840] workqueue events_freezable_power_: flags=0x84
> > [  272.862461]   pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256
> > [  272.864479]     in-flight: 11286:disk_events_workfn
> 
> What's this guy doing?  Can you get stack dump on 11286 (or whatever
> is in flight in the next lockup)?

Wait, this series doesn't include Tetsuo's change.  Of course it won't
fix the deadlock problem.  What's necessary is Tetsuo's patch +
WQ_MEM_RECLAIM.

Thanks.

-- 
tejun

  reply	other threads:[~2015-10-29  3:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  2:41 [patch 0/3] vmstat: Various enhancements Christoph Lameter
2015-10-28  2:41 ` Christoph Lameter
2015-10-28  2:41 ` [patch 1/3] vmstat: Make pageset processing optional in refresh_cpu_vm_stats Christoph Lameter
2015-10-28  2:41   ` Christoph Lameter
2015-10-28  2:41 ` [patch 2/3] vmstat: make vmstat_updater deferrable again and shut down on idle Christoph Lameter
2015-10-28  2:41   ` Christoph Lameter
2015-10-28  2:41 ` [patch 3/3] vmstat: Create our own workqueue Christoph Lameter
2015-10-28  2:41   ` Christoph Lameter
2015-10-28  2:43   ` Tejun Heo
2015-10-28  2:43     ` Tejun Heo
2015-10-28  3:04     ` Christoph Lameter
2015-10-28  3:04       ` Christoph Lameter
2015-10-28 11:57       ` Tetsuo Handa
2015-10-28 11:57         ` Tetsuo Handa
2015-10-28 22:32         ` Christoph Lameter
2015-10-28 22:32           ` Christoph Lameter
2015-10-29  2:24         ` Tejun Heo
2015-10-29  2:24           ` Tejun Heo
2015-10-29  3:08           ` Tejun Heo [this message]
2015-10-29  3:08             ` Tejun Heo
2015-10-30  1:01             ` Christoph Lameter
2015-10-30  1:01               ` Christoph Lameter
2015-10-31  1:15               ` Tejun Heo
2015-10-31  1:15                 ` Tejun Heo
2015-10-31  2:43               ` Tetsuo Handa
2015-10-31  2:43                 ` Tetsuo Handa
2015-11-02 16:12                 ` Christoph Lameter
2015-11-02 16:12                   ` Christoph Lameter
2015-11-02 16:52                   ` Tetsuo Handa
2015-11-02 16:52                     ` Tetsuo Handa
2015-11-02 18:10                     ` Christoph Lameter
2015-11-02 18:10                       ` Christoph Lameter
2015-11-02 19:11                       ` Tejun Heo
2015-11-02 19:11                         ` Tejun Heo
2015-11-06 11:28                   ` Tetsuo Handa
2015-11-06 11:28                     ` Tetsuo Handa
2015-11-06 12:56                     ` Christoph Lameter
2015-11-06 12:56                       ` 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=20151029030822.GD27115@mtj.duckdns.org \
    --to=htejun@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=torvalds@linux-foundation.org \
    /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.