commit | 3834d721762d3cba1634e04c790867a0b7de6a82 | [log] [tgz] |
---|---|---|
author | Manupa Karunaratne <manupa.karunaratne@arm.com> | Tue Oct 05 00:50:03 2021 +0100 |
committer | GitHub <noreply@github.com> | Mon Oct 04 16:50:03 2021 -0700 |
tree | 16dede345af933766b680b0d8f49d2686b5ebeb2 | |
parent | cfdf1df84c5ab884d88a181f24dcae783c31f8c8 [diff] |
[RFC] TVM Unified Static Memory Planning (#9) * [RFC] TVM Unified Static Memory Planning This commits adds the RFC (.md) for USMP * [RFC] TVM Unified Static Memory Planning *Updating the RFC with PR number * [RFC] TVM Unified Static Memory Planning * addressing tristan's comments. Change-Id: Ieb64ae6fc1de12374836c7f754a70b735fe5d379 * [RFC] TVM Unified Static Memory Planning *Addressing further tristan's comments Change-Id: I5eabfda362fa85fa4c377d20043f938ffc6de456 * [RFC] TVM Unified Static Memory Planning * addressed comments Change-Id: I12fa85e5ea10eee328be4c5d51c9a481a90dedb5 * [RFC] TVM Unified Static Memory Planning *reflecting the partial changes for tir pinned memory representation *addressing Andrew's comments Change-Id: I40019ecb8e75ba46b1bf415ea70718bbeab3d26b * [RFC] TVM Unified Static Memory Planning *explaining the fallback and candidate_memory_pools Change-Id: Iab59de953bd931fe44ae77004f8c014e25b126f8 * [RFC] TVM Unified Static Memory Planning * Improving text * Adding more specifics to how to handle fallback pool * Renamed TVMC arugments to be pools instead of buffer
An RFC is a “Request for Change” to the TVM project. It is a design document that describes a new feature, enhancement, or process to the TVM project. RFCs should be the primary mechanism for proposing major features and changes. The author of the RFC is responsible for the discussion of the change, and for organizing the work around it. RFCs are text files, stored in the Apache TVM RFC repository, that serve as history and documentation of TVM features.
The primary audience of RFCs is the TVM development community. RFCs serve as a guide for the design and implementation of features during and after their development. A secondary audience is general users and developers who are interested in how and why a feature was designed and implemented.
To work on a major feature within the TVM project, an RFC must first be merged into the TVM RFC repository as a markdown file. Once merged, the RFC is considered to be “active” and may be implemented, with the goal of merging the implementation into the TVM project. These are steps that should be taken in the RFC process:
tvm-rfcs
repository. To allocate a new RFC number, open a PR against tvm-rfcs
(initially, you might need to use a dummy number in the filename for the RFC content; this can be updated after the RFC PR is created).L
to indicate it is a legacy RFC. For example, L0001
.Apache TVM is a compiler stack for deep learning systems. It is designed to close the gap between the productivity-focused deep learning frameworks, and the performance- and efficiency-focused hardware backends. TVM works with deep learning frameworks to provide end to end compilation to different backends.
© Contributors Licensed under an Apache-2.0 license.
TVM adopts Apache committer model. We aim to create an open source project that is maintained and owned by the community. Check out the Contributor Guide.