linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qi Zheng <zhengqi.arch@bytedance.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, rafael@kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, songmuchun@bytedance.com
Subject: Re: [PATCH 2/2] mm: reimplement si_mem_available()
Date: Thu, 16 Dec 2021 23:39:02 +0800	[thread overview]
Message-ID: <10a38fe0-d609-0e25-4a79-a5d23a83600b@bytedance.com> (raw)
In-Reply-To: <Ybs8WBHt+5TklFe8@kroah.com>



On 12/16/21 9:17 PM, Greg KH wrote:
> On Thu, Dec 16, 2021 at 08:46:55PM +0800, Qi Zheng wrote:
>> Reimplement si_mem_available() by reusing si_mem_available_node().
> 
> That says what you did, but not why.  Why are you doing this?

Oh, sorry, I will add that.

> 
> And what does it have to do with patch 1/2?

With [PATCH 1/2], we can simply sum the MemAvailable of each node
to get the gobal MemAvailable. Essentially this is a cleanup, no
functional changes.

Thanks,
Qi

> 
> thanks,
> 
> greg k-h
> 

-- 
Thanks,
Qi

  reply	other threads:[~2021-12-16 15:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 12:46 [PATCH 0/2] add MemAvailable to per-node meminfo Qi Zheng
2021-12-16 12:46 ` [PATCH 1/2] mm: " Qi Zheng
2021-12-16 13:16   ` Greg KH
2021-12-16 15:31     ` Qi Zheng
2021-12-16 15:37       ` Greg KH
2021-12-16 15:43         ` Qi Zheng
2021-12-16 12:46 ` [PATCH 2/2] mm: reimplement si_mem_available() Qi Zheng
2021-12-16 13:17   ` Greg KH
2021-12-16 15:39     ` Qi Zheng [this message]
2021-12-16 15:06   ` kernel test robot
2021-12-16 18:21   ` kernel test robot
2021-12-16 21:05   ` kernel test robot

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=10a38fe0-d609-0e25-4a79-a5d23a83600b@bytedance.com \
    --to=zhengqi.arch@bytedance.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rafael@kernel.org \
    --cc=songmuchun@bytedance.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;
as well as URLs for NNTP newsgroup(s).