Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update layout constraint explanation #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update layout constraint explanation #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 8 additions & 10 deletions circuit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -380,16 +380,14 @@ for AVX or FMA instruction extensions.

At this point, the observant reader will notice that we
have done nothing to actually specify that our
physical instances should be laid out in struct-of-arrays
order. To accomplish this we extend the `DefaultMapper`
with a custom `CircuitMapper`. In the `map_task` method,
we modify the mapping requests for each `RegionRequirement`
to specify that the `blocking_factor` should be set to
the `max_blocking_factor` allowed. This will tell the
runtime that a struct-of-arrays layout should be used.
If we had specified `1` for the blocking factor, that
would correspond to an `AOS` layout, and any value in
between would be a `HybridSOA` layout.
physical instances should be laid out in struct-of-arrays (SOA)
order. The default mapper uses the SOA format to encourage maximum re-use
by any tasks which use subsets of the fields. Actually users can specify
the layout constraint for each task variant during task registration time,
an example of which is the [here](https://github.com/StanfordLegion/legion/blob/stable/examples/layout_constraints/transpose.cc).
Another way to change the layout constraint is to extend the `DefaultMapper`
with a custom mapper. In the `map_task` method,
we could specify the `OrderingConstraint`.

#### GPU Execution ####

Expand Down