mm, rebasing snafu. Here's updated patch:
8<
>From 10ac187717494a086b961a8c1eaea17e091180a2 Mon Sep 17 00:00:00 2001
From: Vlastimil Babka <vba...@suse.cz>
Date: Mon, 2 May 2016 15:40:29 +0200
Subject: [PATCH v3 07/17] mm, compaction: introduce direct compaction priority
In th
mm, rebasing snafu. Here's updated patch:
8<
>From 10ac187717494a086b961a8c1eaea17e091180a2 Mon Sep 17 00:00:00 2001
From: Vlastimil Babka
Date: Mon, 2 May 2016 15:40:29 +0200
Subject: [PATCH v3 07/17] mm, compaction: introduce direct compaction priority
In the context of direct co
Hi,
[auto build test ERROR on next-20160624]
[cannot apply to tip/perf/core v4.7-rc4 v4.7-rc3 v4.7-rc2 v4.7-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test ERROR on next-20160624]
[cannot apply to tip/perf/core v4.7-rc4 v4.7-rc3 v4.7-rc2 v4.7-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
In the context of direct compaction, for some types of allocations we would
like the compaction to either succeed or definitely fail while trying as hard
as possible. Current async/sync_light migration mode is insufficient, as there
are heuristics such as caching scanner positions, marking
In the context of direct compaction, for some types of allocations we would
like the compaction to either succeed or definitely fail while trying as hard
as possible. Current async/sync_light migration mode is insufficient, as there
are heuristics such as caching scanner positions, marking
6 matches
Mail list logo
