You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bc2833f
Browse filesBrowse the repository at this point in the historyBrowse files
Arm backend: Move memory pools into NOLOAD section (pytorch#21741)
In the arm_executor_runner, the two large memory pools (60MiB by
default) input_file_allocation_pool and
memory_allocation_pool were put into the input_data_sec section. While
the pools contain uninitialized memory, this section is also used for
embedding data into the runner and can thus not be NOLOAD.
Instead, introduce two new input sections,
input_file_allocator_sec and method_allocator_sec, that are put into
.ddr.bss which is already NOLOAD.
Additionally, for Corstone-300 the .ddr.bss output section is placed
after the DDR-backed scatter-load payloads to avoid creating a large
file-backed hole in the ELF.
This saves binary size, since the pools
will only be initialized at runtime. It also has the benefit of making
the placement of these pools more explicit.
cc @digantdesai@freddan80@per@zingo@oscarandersson8218@mansnils@Sebastian-Larsson@robell@rascani
Signed-off-by: Erik Lundell <erik.lundell@arm.com>
0 commit comments