From 13166eaa824d817ad7faa12871a3600373885e0c Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Mon, 31 Jul 2023 16:30:51 +0100 Subject: [PATCH] Update text/0001-agile-coretime.md --- text/0001-agile-coretime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0001-agile-coretime.md b/text/0001-agile-coretime.md index 8640d8a..dd1a6d2 100644 --- a/text/0001-agile-coretime.md +++ b/text/0001-agile-coretime.md @@ -464,7 +464,7 @@ struct InstaPoolHistoryRecord { type InstaPoolHistory = Map; ``` -`CoreMask` tracks unique "parts" of a single core. It is used with interlacing in order to give a unique identifier to each compnent of any possible interlacing configuration of a core, allowing for simple self-describing keys for all core ownership and allocation information. It also allows for each core's workload to be tracked and updated progressively, keeping ongoing compute costs well-bounded and low. +`CoreMask` tracks unique "parts" of a single core. It is used with interlacing in order to give a unique identifier to each component of any possible interlacing configuration of a core, allowing for simple self-describing keys for all core ownership and allocation information. It also allows for each core's workload to be tracked and updated progressively, keeping ongoing compute costs well-bounded and low. Regions are issued into the `Regions` map and can be transferred, partitioned and interlaced as the owner desires. Regions can only be tasked if they begin after the current scheduling deadline (if they have missed this, then the region can be auto-trimmed until it is).