linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Waiman Long <longman@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Alex Shi <alex.shi@linux.alibaba.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/filemap: Adding missing mem_cgroup_uncharge() to __add_to_page_cache_locked()
Date: Mon, 25 Jan 2021 19:31:05 +0100	[thread overview]
Message-ID: <20210125183105.GW827@dhcp22.suse.cz> (raw)
In-Reply-To: <53eb7692-e559-a914-e103-adfe951d7a7c@redhat.com>

On Mon 25-01-21 13:23:58, Waiman Long wrote:
> On 1/25/21 1:14 PM, Michal Hocko wrote:
[...]
> > With the proposed simplification by Willy
> > Acked-by: Michal Hocko <mhocko@suse.com>
> 
> Thank for the ack. However, I am a bit confused about what you mean by
> simplification. There is another linux-next patch that changes the condition
> for mem_cgroup_charge() to

This is obviously a fix and I believe should go in the next rc while
secretmem is a new feature which should wait at least to the next merge
window.

> -       if (!huge) {
> +       if (!huge && !page_is_secretmem(page)) {
>                 error = mem_cgroup_charge(page, current->mm, gfp);
> 
> That is the main reason why I introduced the boolean variable as I don't
> want to call the external page_is_secretmem() function twice.
> 
> Cheers,
> Longman
> 

-- 
Michal Hocko
SUSE Labs


  parent reply	other threads:[~2021-01-25 18:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25  4:24 Waiman Long
2021-01-25  4:36 ` Matthew Wilcox
2021-01-25  6:34   ` Miaohe Lin
2021-01-25 14:09   ` Waiman Long
2021-01-25  4:41 ` Alex Shi
2021-01-25  6:30 ` Miaohe Lin
2021-01-25 14:12   ` Waiman Long
2021-01-25 23:11     ` Andrew Morton
2021-01-25 23:13       ` Waiman Long
2021-01-25  8:07 ` Muchun Song
2021-01-25 15:35   ` Waiman Long
2021-01-25  9:28 ` Michal Hocko
2021-01-25 15:57   ` Waiman Long
2021-01-25 16:03     ` Michal Hocko
2021-01-25 16:25       ` Matthew Wilcox
2021-01-25 16:41         ` Michal Hocko
2021-01-25 18:14           ` Michal Hocko
2021-01-25 18:23             ` Waiman Long
2021-01-25 18:29               ` Matthew Wilcox
2021-01-25 18:45                 ` Waiman Long
2021-01-25 18:31               ` Michal Hocko [this message]
2021-01-25 18:52               ` Johannes Weiner
2021-01-25 18:57                 ` Waiman Long
2021-01-26  8:01                   ` Michal Hocko
2021-01-25 18:43           ` Johannes Weiner

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=20210125183105.GW827@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.shi@linux.alibaba.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=longman@redhat.com \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox