From: Keith Busch <keith.busch@intel.com>
To: "shhuiw@foxmail.com" <shhuiw@foxmail.com>
Cc: "iamjoonsoo.kim" <iamjoonsoo.kim@lge.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: Re: why use alloc_workqueue instead of create_singlethread_workqueue to create nvme_workq
Date: Wed, 1 Jun 2016 10:34:12 -0400 [thread overview]
Message-ID: <20160601143412.GJ24107@localhost.localdomain> (raw)
In-Reply-To: <2016060110542407705011@foxmail.com>
On Wed, Jun 01, 2016 at 10:54:27AM +0800, shhuiw@foxmail.com wrote:
> Thanks, Keith!
>
> Any idea on how to fix the warning? Just drop the WQ_MEM_RECLAIM for nvme_workq, or
> lru drain work schedule should be changed?
I sent request to lkml and linux-mm list, trying to resurrect this older
proposal from Tejun Heo:
https://patchwork.ozlabs.org/patch/574623/
Not much interest yet, though.
--
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>
prev parent reply other threads:[~2016-06-01 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_4323E1CE03D759181B6B4507@qq.com>
[not found] ` <20160531145306.GB24107@localhost.localdomain>
2016-06-01 2:54 ` shhuiw
2016-06-01 14:34 ` Keith Busch [this message]
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=20160601143412.GJ24107@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=shhuiw@foxmail.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