Skip to content

Commit a96d1b4

Browse files
Address Mike's remarks
1 parent 3a2f55b commit a96d1b4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

rfcs/proposed/numa_support/numa-arenas-creation-and-use.org

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ for(unsigned j = 0; j < numa_indexes.size(); j++) {
2626

2727
Usually the users of oneTBB employ this technique to tie oneTBB worker threads
2828
up within NUMA nodes and yet have all the parallelism of a platform utilized.
29-
The pattern allows to find out how many NUMA nodes are on the system. With that
30-
number user creates that many ~tbb::task_arena~ objects, constraining each to a
29+
The pattern starts by finding the number of NUMA nodes on the system. With that
30+
number, user creates that many ~tbb::task_arena~ objects, constraining each to a
3131
dedicated NUMA node. Along with ~tbb::task_arena~ objects user instantiates the
3232
same number of ~tbb::task_group~ objects, with which the oneTBB tasks are going
3333
to be associated. The ~tbb::task_group~ objects are needed because they allow

0 commit comments

Comments
 (0)