diff options
| author | Connor Doyle <connor.p.doyle@intel.com> | 2018-10-02 10:32:00 -0700 |
|---|---|---|
| committer | Connor Doyle <connor.p.doyle@intel.com> | 2018-10-02 10:32:00 -0700 |
| commit | d96c2fb5cdc91f763719d6b5b51351f769cc543b (patch) | |
| tree | 942f3b89f3c65ebabea41d0f5c87ed9947e1600b | |
| parent | 7ac4fbfaa6a92160eb4ca632047bf24a69df99dc (diff) | |
Fix spelling error.
| -rw-r--r-- | contributors/design-proposals/node/topology-manager.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/design-proposals/node/topology-manager.md b/contributors/design-proposals/node/topology-manager.md index 4647b5b6..3373a8e2 100644 --- a/contributors/design-proposals/node/topology-manager.md +++ b/contributors/design-proposals/node/topology-manager.md @@ -155,7 +155,7 @@ graduation from alpha to beta. #### Computing Preferred Affinity A topology hint indicates a preference for some well-known local resources. -Initally, the only supported reference resource is a mask of CPU socket IDs. +Initially, the only supported reference resource is a mask of CPU socket IDs. After collecting hints from all providers, the Topology Manager chooses some mask that is present in all lists. Here is a sketch: @@ -273,7 +273,7 @@ _Topology Manager fetches affinity from hint providers._ * Testing the Topology Manager in a continuous integration environment depends on cloud infrastructure to expose multi-node topologies to guest virtual machines. -* Implementing the `GetTopologyHints()` interface may prove challenging. +* Implementing the `GetHints()` interface may prove challenging. # Limitations |