All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@suse.cz>, Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Rientjes <rientjes@google.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Rik van Riel <riel@redhat.com>,
	Andrew Shewmaker <agshew@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>, Namjae Jeon <linkinjeon@gmail.com>,
	Jan Kara <jack@suse.cz>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/7] mm/writeback: commit reason of WB_REASON_FORKER_THREAD mismatch name
Date: Mon, 17 Jun 2013 17:41:44 +0800	[thread overview]
Message-ID: <20130617094144.GA21564@hacker.(null)> (raw)
In-Reply-To: <20130617083030.GE19194@dhcp22.suse.cz>

On Mon, Jun 17, 2013 at 10:30:30AM +0200, Michal Hocko wrote:
>On Sun 16-06-13 09:14:46, Wanpeng Li wrote:
>> After commit 839a8e86("writeback: replace custom worker pool implementation
>> with unbound workqueue"), there is no bdi forker thread any more. However,
>> WB_REASON_FORKER_THREAD is still used due to it is somewhat userland visible 
>
>What exactly "somewhat userland visible" means?
>Is this about trace events?

Thanks for the question, Tejun, could you explain this for us? ;-)

Regards,
Wanpeng Li 

>
>> and we won't be exposing exactly the same information with just a different 
>> name. 
>> 
>> Signed-off-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>
>> ---
>>  include/linux/writeback.h | 5 +++++
>>  1 file changed, 5 insertions(+)
>> 
>> diff --git a/include/linux/writeback.h b/include/linux/writeback.h
>> index 8b5cec4..cf077a7 100644
>> --- a/include/linux/writeback.h
>> +++ b/include/linux/writeback.h
>> @@ -47,6 +47,11 @@ enum wb_reason {
>>  	WB_REASON_LAPTOP_TIMER,
>>  	WB_REASON_FREE_MORE_MEM,
>>  	WB_REASON_FS_FREE_SPACE,
>> +/*
>> + * There is no bdi forker thread any more and works are done by emergency
>> + * worker, however, this is somewhat userland visible and we'll be exposing
>> + * exactly the same information, so it has a mismatch name.
>> + */
>>  	WB_REASON_FORKER_THREAD,
>>  
>>  	WB_REASON_MAX,
>> -- 
>> 1.8.1.2
>> 
>
>-- 
>Michal Hocko
>SUSE Labs

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

  reply	other threads:[~2013-06-17  9:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16  1:14 [PATCH v2 1/7] mm/writeback: remove wb_reason_name Wanpeng Li
2013-06-16  1:14 ` Wanpeng Li
2013-06-16  1:14 ` [PATCH v2 2/7] mm/writeback: Don't check force_wait to handle bdi->work_list Wanpeng Li
2013-06-16  1:14   ` Wanpeng Li
2013-06-16  1:14 ` [PATCH v2 3/7] mm/writeback: commit reason of WB_REASON_FORKER_THREAD mismatch name Wanpeng Li
2013-06-16  1:14   ` Wanpeng Li
2013-06-17  8:30   ` Michal Hocko
2013-06-17  8:30     ` Michal Hocko
2013-06-17  9:41     ` Wanpeng Li [this message]
2013-06-17  9:41     ` Wanpeng Li
     [not found]     ` <51bed9eb.41e9420a.2725.ffff943cSMTPIN_ADDED_BROKEN@mx.google.com>
2013-06-17 20:27       ` Tejun Heo
2013-06-17 20:27         ` Tejun Heo
2013-06-16  1:14 ` [PATCH v2 4/7] mm/page_alloc: fix blank in show_free_areas Wanpeng Li
2013-06-16  1:14   ` Wanpeng Li
2013-06-17  8:10   ` Michal Hocko
2013-06-17  8:10     ` Michal Hocko
2013-06-17  9:50     ` Wanpeng Li
2013-06-17  9:50     ` Wanpeng Li
2013-06-16  1:14 ` [PATCH v2 5/7] mm/page_alloc: fix doc for numa_zonelist_order Wanpeng Li
2013-06-16  1:14   ` Wanpeng Li
2013-06-17  8:17   ` Michal Hocko
2013-06-17  8:17     ` Michal Hocko
2013-06-16  1:14 ` [PATCH v2 6/7] mm/thp: fix doc for transparent huge zero page Wanpeng Li
2013-06-16  1:14   ` Wanpeng Li
2013-06-16  1:14 ` [PATCH v2 7/7] mm/pgtable: Don't accumulate addr during pgd prepopulate pmd Wanpeng Li
2013-06-16  1:14   ` Wanpeng Li
2013-06-17  8:20   ` Michal Hocko
2013-06-17  8:20     ` Michal Hocko

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='20130617094144.GA21564@hacker.(null)' \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=agshew@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=jack@suse.cz \
    --cc=jkosina@suse.cz \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=tj@kernel.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.