Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1601831 > unrolled thread

Re: [PATCH v3 2/8] mm, compaction: remove redundant watermark check in compact_finished()

Started byJoonsoo Kim <iamjoonsoo.kim@lge.com>
First post2017-03-16 02:30 +0100
Last post2017-03-16 02:30 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v3 2/8] mm, compaction: remove redundant watermark check  in compact_finished() Joonsoo Kim <iamjoonsoo.kim@lge.com> - 2017-03-16 02:30 +0100

#1601831 — Re: [PATCH v3 2/8] mm, compaction: remove redundant watermark check in compact_finished()

FromJoonsoo Kim <iamjoonsoo.kim@lge.com>
Date2017-03-16 02:30 +0100
SubjectRe: [PATCH v3 2/8] mm, compaction: remove redundant watermark check in compact_finished()
Message-ID<tlsoN-7DD-5@gated-at.bofh.it>
Hello,

On Tue, Mar 07, 2017 at 02:15:39PM +0100, Vlastimil Babka wrote:
> When detecting whether compaction has succeeded in forming a high-order page,
> __compact_finished() employs a watermark check, followed by an own search for
> a suitable page in the freelists. This is not ideal for two reasons:
> 
> - The watermark check also searches high-order freelists, but has a less strict
>   criteria wrt fallback. It's therefore redundant and waste of cycles. This was
>   different in the past when high-order watermark check attempted to apply
>   reserves to high-order pages.

Although it looks redundant now, I don't like removal of the watermark
check here. Criteria in watermark check would be changed to more strict
later and we would easily miss to apply it on compaction side if the
watermark check is removed.

> 
> - The watermark check might actually fail due to lack of order-0 pages.
>   Compaction can't help with that, so there's no point in continuing because of
>   that. It's possible that high-order page still exists and it terminates.

If lack of order-0 pages is the reason for stopping compaction, we
need to insert the watermark check for order-0 to break the compaction
instead of removing it. Am I missing something?

Thanks.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web