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


Groups > linux.kernel > #1370504

Re: [PATCH v2 4/4] mm, compaction: direct freepage allocation for async direct compaction

From Mel Gorman <mgorman@techsingularity.net>
Newsgroups linux.kernel
Subject Re: [PATCH v2 4/4] mm, compaction: direct freepage allocation for async direct compaction
Date 2016-04-04 11:40 +0200
Message-ID <rk99g-118-15@gated-at.bofh.it> (permalink)
References <riGCm-2kC-13@gated-at.bofh.it> <riGCn-2kC-35@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Thu, Mar 31, 2016 at 10:50:36AM +0200, Vlastimil Babka wrote:
> The goal of direct compaction is to quickly make a high-order page available
> for the pending allocation. The free page scanner can add significant latency
> when searching for migration targets, although to succeed the compaction, the
> only important limit on the target free pages is that they must not come from
> the same order-aligned block as the migrated pages.
> 

What prevents the free pages being allocated from behind the migration
scanner? Having compaction abort when the scanners meet misses
compaction opportunities but it avoids the problem of Compactor A using
pageblock X as a migration target and Compactor B using pageblock X as a
migration source.

-- 
Mel Gorman
SUSE Labs

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH v2 4/4] mm, compaction: direct freepage allocation for  async direct compaction Mel Gorman <mgorman@techsingularity.net> - 2016-04-04 11:40 +0200
  Re: [PATCH v2 4/4] mm, compaction: direct freepage allocation for  async direct compaction Vlastimil Babka <vbabka@suse.cz> - 2016-04-04 13:10 +0200

csiph-web