All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov@parallels.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, glommer@gmail.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	devel@openvz.org
Subject: Re: [PATCH -mm 3/4] fork: charge threadinfo to memcg explicitly
Date: Thu, 27 Mar 2014 11:39:18 +0400	[thread overview]
Message-ID: <5333D5A6.8090409@parallels.com> (raw)
In-Reply-To: <20140326220050.GC22656@dhcp22.suse.cz>

On 03/27/2014 02:00 AM, Michal Hocko wrote:
> On Wed 26-03-14 19:28:06, Vladimir Davydov wrote:
>> We have only a few places where we actually want to charge kmem so
>> instead of intruding into the general page allocation path with
>> __GFP_KMEMCG it's better to explictly charge kmem there. All kmem
>> charges will be easier to follow that way.
>>
>> This is a step toward removing __GFP_KMEMCG. It makes fork charge task
>> threadinfo pages explicitly instead of passing __GFP_KMEMCG to
>> alloc_pages.
> Looks good from a quick glance. I would also remove
> THREADINFO_GFP_ACCOUNTED in this patch.

To do so,  I'd have to remove __GFP_KMEMCG check from
memcg_kmem_newpage_charge, which is better to do in the next patch,
which removes __GFP_KMEMCG everywhere, IMO.

Thanks.

>> Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
>> Cc: Johannes Weiner <hannes@cmpxchg.org>
>> Cc: Michal Hocko <mhocko@suse.cz>
>> Cc: Glauber Costa <glommer@gmail.com>
>> ---
>>  kernel/fork.c |   13 ++++++++++---
>>  1 file changed, 10 insertions(+), 3 deletions(-)
>>
>> diff --git a/kernel/fork.c b/kernel/fork.c
>> index f4b09bc15f3a..8209780cf732 100644
>> --- a/kernel/fork.c
>> +++ b/kernel/fork.c
>> @@ -150,15 +150,22 @@ void __weak arch_release_thread_info(struct thread_info *ti)
>>  static struct thread_info *alloc_thread_info_node(struct task_struct *tsk,
>>  						  int node)
>>  {
>> -	struct page *page = alloc_pages_node(node, THREADINFO_GFP_ACCOUNTED,
>> -					     THREAD_SIZE_ORDER);
>> +	struct page *page;
>> +	struct mem_cgroup *memcg = NULL;
>>  
>> +	if (!memcg_kmem_newpage_charge(THREADINFO_GFP_ACCOUNTED, &memcg,
>> +				       THREAD_SIZE_ORDER))
>> +		return NULL;
>> +	page = alloc_pages_node(node, THREADINFO_GFP, THREAD_SIZE_ORDER);
>> +	memcg_kmem_commit_charge(page, memcg, THREAD_SIZE_ORDER);
>>  	return page ? page_address(page) : NULL;
>>  }
>>  
>>  static inline void free_thread_info(struct thread_info *ti)
>>  {
>> -	free_memcg_kmem_pages((unsigned long)ti, THREAD_SIZE_ORDER);
>> +	if (ti)
>> +		memcg_kmem_uncharge_pages(virt_to_page(ti), THREAD_SIZE_ORDER);
>> +	free_pages((unsigned long)ti, THREAD_SIZE_ORDER);
>>  }
>>  # else
>>  static struct kmem_cache *thread_info_cache;
>> -- 
>> 1.7.10.4
>>

--
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: Vladimir Davydov <vdavydov@parallels.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: <akpm@linux-foundation.org>, <hannes@cmpxchg.org>,
	<glommer@gmail.com>, <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>, <devel@openvz.org>
Subject: Re: [PATCH -mm 3/4] fork: charge threadinfo to memcg explicitly
Date: Thu, 27 Mar 2014 11:39:18 +0400	[thread overview]
Message-ID: <5333D5A6.8090409@parallels.com> (raw)
In-Reply-To: <20140326220050.GC22656@dhcp22.suse.cz>

On 03/27/2014 02:00 AM, Michal Hocko wrote:
> On Wed 26-03-14 19:28:06, Vladimir Davydov wrote:
>> We have only a few places where we actually want to charge kmem so
>> instead of intruding into the general page allocation path with
>> __GFP_KMEMCG it's better to explictly charge kmem there. All kmem
>> charges will be easier to follow that way.
>>
>> This is a step toward removing __GFP_KMEMCG. It makes fork charge task
>> threadinfo pages explicitly instead of passing __GFP_KMEMCG to
>> alloc_pages.
> Looks good from a quick glance. I would also remove
> THREADINFO_GFP_ACCOUNTED in this patch.

To do so,  I'd have to remove __GFP_KMEMCG check from
memcg_kmem_newpage_charge, which is better to do in the next patch,
which removes __GFP_KMEMCG everywhere, IMO.

Thanks.

>> Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
>> Cc: Johannes Weiner <hannes@cmpxchg.org>
>> Cc: Michal Hocko <mhocko@suse.cz>
>> Cc: Glauber Costa <glommer@gmail.com>
>> ---
>>  kernel/fork.c |   13 ++++++++++---
>>  1 file changed, 10 insertions(+), 3 deletions(-)
>>
>> diff --git a/kernel/fork.c b/kernel/fork.c
>> index f4b09bc15f3a..8209780cf732 100644
>> --- a/kernel/fork.c
>> +++ b/kernel/fork.c
>> @@ -150,15 +150,22 @@ void __weak arch_release_thread_info(struct thread_info *ti)
>>  static struct thread_info *alloc_thread_info_node(struct task_struct *tsk,
>>  						  int node)
>>  {
>> -	struct page *page = alloc_pages_node(node, THREADINFO_GFP_ACCOUNTED,
>> -					     THREAD_SIZE_ORDER);
>> +	struct page *page;
>> +	struct mem_cgroup *memcg = NULL;
>>  
>> +	if (!memcg_kmem_newpage_charge(THREADINFO_GFP_ACCOUNTED, &memcg,
>> +				       THREAD_SIZE_ORDER))
>> +		return NULL;
>> +	page = alloc_pages_node(node, THREADINFO_GFP, THREAD_SIZE_ORDER);
>> +	memcg_kmem_commit_charge(page, memcg, THREAD_SIZE_ORDER);
>>  	return page ? page_address(page) : NULL;
>>  }
>>  
>>  static inline void free_thread_info(struct thread_info *ti)
>>  {
>> -	free_memcg_kmem_pages((unsigned long)ti, THREAD_SIZE_ORDER);
>> +	if (ti)
>> +		memcg_kmem_uncharge_pages(virt_to_page(ti), THREAD_SIZE_ORDER);
>> +	free_pages((unsigned long)ti, THREAD_SIZE_ORDER);
>>  }
>>  # else
>>  static struct kmem_cache *thread_info_cache;
>> -- 
>> 1.7.10.4
>>


  reply	other threads:[~2014-03-27  7:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 15:28 [PATCH -mm 0/4] kmemcg: get rid of __GFP_KMEMCG Vladimir Davydov
2014-03-26 15:28 ` Vladimir Davydov
2014-03-26 15:28 ` [PATCH -mm 1/4] sl[au]b: do not charge large allocations to memcg Vladimir Davydov
2014-03-26 15:28   ` Vladimir Davydov
2014-03-26 21:53   ` Michal Hocko
2014-03-26 21:53     ` Michal Hocko
2014-03-27  7:34     ` Vladimir Davydov
2014-03-27  7:34       ` Vladimir Davydov
2014-03-27 20:40       ` Michal Hocko
2014-03-27 20:40         ` Michal Hocko
2014-03-27  4:31   ` Greg Thelen
2014-03-27  4:31     ` Greg Thelen
2014-03-27  7:37     ` Vladimir Davydov
2014-03-27  7:37       ` Vladimir Davydov
2014-03-27 20:42       ` Greg Thelen
2014-03-27 20:42         ` Greg Thelen
2014-03-28  7:56         ` Vladimir Davydov
2014-03-28  7:56           ` Vladimir Davydov
2014-03-27 20:43       ` Michal Hocko
2014-03-27 20:43         ` Michal Hocko
2014-03-28  7:58         ` Vladimir Davydov
2014-03-28  7:58           ` Vladimir Davydov
2014-03-26 15:28 ` [PATCH -mm 2/4] sl[au]b: charge slabs to memcg explicitly Vladimir Davydov
2014-03-26 15:28   ` Vladimir Davydov
2014-03-26 21:58   ` Michal Hocko
2014-03-26 21:58     ` Michal Hocko
2014-03-27  7:38     ` Vladimir Davydov
2014-03-27  7:38       ` Vladimir Davydov
2014-03-27 20:38       ` Michal Hocko
2014-03-27 20:38         ` Michal Hocko
2014-03-26 15:28 ` [PATCH -mm 3/4] fork: charge threadinfo " Vladimir Davydov
2014-03-26 15:28   ` Vladimir Davydov
2014-03-26 22:00   ` Michal Hocko
2014-03-26 22:00     ` Michal Hocko
2014-03-27  7:39     ` Vladimir Davydov [this message]
2014-03-27  7:39       ` Vladimir Davydov
2014-03-26 15:28 ` [PATCH -mm 4/4] mm: kill __GFP_KMEMCG Vladimir Davydov
2014-03-26 15:28   ` Vladimir Davydov

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=5333D5A6.8090409@parallels.com \
    --to=vdavydov@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=devel@openvz.org \
    --cc=glommer@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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.