A Partition is an attribute on a source instance to enable reuse.
Partitions can be instances in HDL, Schematic or EDIF sources at any
level of the hierarchy. When a lower-level source instance is defined
as a Partition the top level module automatically becomes a Partition.
When a Partition is created it indicated that the implementation data
for that instance should be reused when possible. For more information
about using Partitions, see
Using Partitions and the
Incremental Design Reuse with Partitions application
note.
Flat vs. Partitioned Design Overview
A Partition
that is preserved will maintain not only identical functionality but
also identical implementation. This will preserve timing of that Partition
so that it does not need to be analyzed or verified again. Partition
preservation may also improve run time compared to implementing the
design again.
Advantages of Partitions
- Partitions enable design preservation based on module instances.
Timing closure will be isolated to a Partition instead of solving
device-wide timing issues.
- Partitions may reduce run-time.
- Since a Partition guarantees exact preservation, timing analysis
and verification is not required for a preserved Partition.