linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "lipeifeng@oppo.com" <lipeifeng@oppo.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	peifengl55 <peifengl55@gmail.com>,
	schwidefsky <schwidefsky@de.ibm.com>,
	"heiko.carstens" <heiko.carstens@de.ibm.com>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	zhangshiming <zhangshiming@oppo.com>,
	guoweichao <guoweichao@oppo.com>,
	zhouhuacai <zhouhuacai@oppo.com>
Subject: Re: [RFC] mm: support multi_freearea to the reduction of external fragmentation
Date: Thu, 22 Apr 2021 11:37:06 +0200	[thread overview]
Message-ID: <0585db50-e8d5-e6d8-9d41-fc398f292d91@redhat.com> (raw)
In-Reply-To: <2021041910374593320011@oppo.com>

On 19.04.21 04:37, lipeifeng@oppo.com wrote:
> Hi Vlastimil Babka:
> Thank you very much indeed for your advice.
> 
> 
> Hi Vlastimil Babka, schwidefsky,heiko.carstens:
> 
> It is a temporary patch to consult experts:
> Is it possible to merge the optimization idea and the implementation
> method to the baseline?

Well, we cannot really say that :)

History taught that merging large and invasive buddy changes is a 
tedious task, can take a long time, and can fail even after a lot of 
discussions and patch series.

Further, usually there has to be a very compelling reason to merge 
large, invasive buddy changes (read: not only optimize very specific 
scenarios); otherwise there will just push back because the invasive 
changes might introduce additional problems or degrade other special 
cases or even the general case.

Last but not least, there have to be more benchmarks and test cases that 
proof that other workload won't be degraded to a degree that people 
care; as one example, this includes runtime overhead when 
allocating/freeing pages.

What usually works best is improving the code in small steps, doing 
minor adjustments but moving into the desired direction.

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2021-04-22  9:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14  2:38 lipeifeng
2021-04-16 11:06 ` Vlastimil Babka
2021-04-19  2:37   ` lipeifeng
2021-04-22  9:37     ` David Hildenbrand [this message]
2021-04-22  9:29   ` David Hildenbrand
2021-04-26  3:19     ` lipeifeng
2021-04-26  8:37       ` David Hildenbrand
2021-04-26 10:19         ` lipeifeng
2021-04-27 12:46           ` David Hildenbrand
2021-04-28  4:03             ` lipeifeng
2021-04-28  9:04               ` David Hildenbrand
2021-04-28 10:53                 ` lipeifeng

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=0585db50-e8d5-e6d8-9d41-fc398f292d91@redhat.com \
    --to=david@redhat.com \
    --cc=guoweichao@oppo.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lipeifeng@oppo.com \
    --cc=peifengl55@gmail.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=vbabka@suse.cz \
    --cc=zhangshiming@oppo.com \
    --cc=zhouhuacai@oppo.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