DREAMPlaceFPGA
DREAMPlaceFPGA
is an Open-Source GPU-Accelerated Placer for Large Scale Heterogeneous FPGAs using a Deep Learning Toolkit.
Placement is a crucial and computationally intensive step in the FPGA design flow that determines the physical locations of various heterogeneous instances in the design. In general, placement consists of three stages - global placement (GP), packing/clustering and legalization (LG), and detailed placement (DP).
With a synthesized logic-mapped design netlist and the FPGA architecture description as inputs, the global placer obtains roughly legal locations for all the design instances. Based on the global placement (GP) solution, the packer clusters the FFs and LUTs to be placed on the corresponding sites. Then, the legalizer assigns all the instances to their corresponding physical sites on the FPGA to obtain a legal placement. A placement is legal when an instance occupies a site of the same type, and all instances can be routed with the limited routed resources available on an FPGA. The disruptive movement of instances to the fixed physical site locations during legalization results in quality degradation, and thus, detailed placement (DP) further refines the legalized placement.
Among the various placement stages, the global placement and pack-legalize stages are accelerated in DREAMPlaceFPGA
.
By leveraging the open-source ASIC placement framework, DREAMPlace, we built an open-source placement framework for FPGAs that is based on the elfPlace algorithm.
The global placement flow in DREAMPlaceFPGA
:
Wirelength, density, and instance area update operators are accelerated on a GPU.
Starting with a flat global placement solution, the direct legalization (DL) algorithm allows for clustering (or) packing of LUTs and FFs, followed by legalization to their respective sites.
The packing-legalization flow in DREAMPlaceFPGA
:
DREAMPlaceFPGA
enhances the DL algorithm and accelerates it on a GPU.
Timing awareness is incorporated in the global placer and packer-legalizer as illustrated:
The timing-driven placer constructs a timing graph for all timing paths as source-load pairs from the design, architecture, and timing model information. In addition to reducing the overall wirelength and overlaps, the global placer optimizes the timing paths once the instance overlaps are minimal.
During a timing GP iteration, the slacks for all the timing arcs are computed based on the current instance locations. Timing criticality is also considered during LUT/FF packing and legalization through cluster scoring functions.
The timing arc wirelength and timing preconditioner operators are accelerated on GPU.
DREAMPlaceFPGA
outperforms elfPlace (GPU) by 19%
for global placementruntime.
On the ISPD'2016 benchmark suite, DREAMPlaceFPGA
is 5.3×
faster for global placement, 2.2×
faster for packing-legalization and 2.4×
faster for overall placement than 16-thread elfPlace (CPU), with a slight increase in (+0.6%) placement HPWL and (+0.9%) routed wirelength.
The timing-driven version (GPU) achieves a 2%
higher post-route geomean critical path delay (CPD), a 3x
faster placement runtime than Vivado 2022.1, and a reduction of Vivado routing runtime by 40%
. Please refer to the 'publications' for more details.
The results vary depending on the hardware used. The above-mentioned results are based on a Linux machine with an Intel i9-7900 CPU (running at 3.30 GHz) and an NVIDIA Titan Xp (Pascal) GPU.
Support for the following architectures is available
DREAMPlaceFPGA
.The elfPlace (CPU) binary is available to run the legalization and detailed placement stages, when
DREAMPlaceFPGA
is used to run only the global placement stage.DREAMPlaceFPGA
runs on both CPU and GPU. If installed on a machine without GPU, multi-threaded CPU support is available.
Zhili Xiong, Rachel Selina Rajarathnam, and David Z. Pan, "A Data-Driven, Congestion-Aware and Open-Source Timing-Driven FPGA Placer Accelerated by GPUs," The 32nd IEEE International Symposium on Field-Programmable Custom Computing Machines (FCCM), 2024. (accepted)
Rachel Selina Rajarathnam, Zixuan Jiang, Mahesh A. Iyer, and David Z. Pan, "DREAMPlaceFPGA-PL
: An Open-Source GPU-Accelerated Packer-Legalizer for Heterogeneous FPGAs", ACM International Symposium on Physical Design (ISPD), 2023.
Rachel Selina Rajarathnam, Mohamed Baker Alawieh, Zixuan Jiang, Mahesh A. Iyer, and David Z. Pan, "DREAMPlaceFPGA
: An Open-Source Analytical Placer for Large Scale Heterogeneous FPGAs using Deep-Learning Toolkit", 27th IEEE/ACM Asian and South Pacific Design Automation Conference (ASP-DAC), 2022.
Rachel Selina Rajarathnam, UTDA, ECE Department, The University of Texas at Austin
Zhili Xiong, UTDA, ECE Department, The University of Texas at Austin
Zhixing (Ethan) Jiang, UTDA, ECE Department, The University of Texas at Austin
Zixuan Jiang, UTDA, ECE Department, The University of Texas at Austin
Python 2.7 or Python 3.5/3.6/3.7
CMake version 3.8.2 or later
Pytorch 1.6/1.7/1.8
CUDA 9.1 or later (Optional)
GPU architecture compatibility 6.0 or later (Optional)
Cairo (Optional)
To pull git submodules in the root directory
git submodule init
git submodule update
Alternatively, pull all the submodules when cloning the repository.
git clone --recursive https://github.com/rachelselinar/DREAMPlaceFPGA.git
There is an alternative way to install DREAMPlaceFPGA using Docker; if you want to use Docker, skip this step and proceed to the next step, "To install with Docker".
At the root directory:
pip install -r requirements.txt
For example, if the repository was cloned in directory ~/Downloads, then the root directory is ~/Downloads/DREAMPlaceFPGA
You can also use a python virtual environment to install all the required packages to run
DREAMPlaceFPGA
You can use the Docker container to avoid building all the dependencies yourself.
docker build . --file Dockerfile --tag <username>/dreamplacefpga:1.0
Replace <username>
with a username, for instance, 'utda_placer.'
Enter the bash environment of the container. Mount the repo and all the Designs into the Docker, which allows the Docker container to access and modify these files directly.
To run on a Linux machine without GPU:
docker run -it -v $(pwd):/DREAMPlaceFPGA <username>/dreamplacefpga:1.0 bash
To run on a Linux machine with GPU: (Docker verified on NVIDIA GPUs with compute capability 6.1, 7.5, and 8.0)
docker run --gpus 1 -it -v $(pwd):/DREAMPlaceFPGA <username>/dreamplacefpga:1.0 bash
For example, to run on a Linux machine without GPU:
docker run -it -v $(pwd):/DREAMPlaceFPGA utda_placer/dreamplacefpga:1.0 bash
DREAMPlaceFPGA
directory in Docker, which is the root directory of the project
cd /DREAMPlaceFPGA
At the root directory,
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=path_to_root_dir
make
make install
If you are using the docker, use these commands at the root directory,
rm -rf build
mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/DREAMPlaceFPGA -DPYTHON_EXECUTABLE=$(which python)
make
make install
Third-party submodules are automatically built except for Boost.
For example,
~/Downloads/DREAMPlaceFPGA: mkdir build; cd build
~/Downloads/DREAMPlaceFPGA/build: cmake . . -DCMAKE_INSTALL_PREFIX=~/Downloads/DREAMPlaceFPGA
~/Downloads/DREAMPlaceFPGA/build: make; make install
The directory ~/Downloads/DREAMPlaceFPGA/build is the install dir
When packages or parser code are changed, the contents of the build directory must be deleted for a clean build and proper operation.
rm -r build
For example,
~/Downloads/DREAMPlaceFPGA: rm -r build
Here are the available options for CMake.
cmake -DCMAKE_INSTALL_PREFIX=path/to/root/directory
cmake -DCMAKE_CUDA_FLAGS=-gencode=arch=compute_60,code=sm_60
cmake -DCMAKE_CXX_ABI=0
DREAMPlaceFPGA
requires IO instances to be fixed and only accepts inputs in Bookshelf format.
DREAMPlaceFPGA
. Refer to IF_README for more details.The sample benchmarks and designs are in the benchmarks directory.
Before running, ensure that all python dependent packages have been installed. Go to the root directory and run with the JSON configuration file.
python dreamplacefpga/Placer.py <benchmark>.json
Run from ~/Downloads/DREAMPlaceFPGA directory
For example:
python dreamplacefpga/Placer.py test/FPGA-example1.json
~/Downloads/DREAMPlaceFPGA: python dreamplacefpga/Placer.py test/FPGA-example1.json
If you are not using the GPU, change the gpu flag in the *.json file to 0.
Unit tests for some of the pytorch operators are provided. For instance, to run the unit test for hpwl, use the below command:
python unitest/ops/hpwl_unitest.py
Note: If your machine does not have an NVIDIA GPU, set the 'gpu' flag in the JSON configuration file to '0' to run on the CPU.
The most frequently used options in the JSON file are listed below. For the complete list of available options, please refer to paramsFPGA.json.
JSON Parameter | Default | Description |
---|---|---|
aux_input | required for bookshelf | input .aux file |
gpu | 1 | enable GPU acceleration or run on CPU |
num_threads | 8 | number of CPU threads |
num_bins_x | 512 | number of bins in horizontal direction |
num_bins_y | 512 | number of bins in vertical direction |
global_place_stages | required | global placement configuration of each stage, a dictionary of {"num_bins_x", "num_bins_y", "iteration", "learning_rate"}, learning_rate is relative to bin size. Note: The maximum number of iterations can be set using "iteration," and the default value is 2000. |
routability_opt_flag | 0 | Set to enable routability optimization. Note: Not setting this flag makes legalization hard for large designs. |
gamma | 5.0 | initial coefficient for log-sum-exp and weighted-average wirelength |
random_seed | 1000 | random seed |
scale_factor | 0.0 | scale factor to avoid numerical overflow; 0.0 means not set |
result_dir | results | result directory for output |
global_place_flag | 1 | whether to run global placement |
legalize_flag | 1 | whether to run legalization on DREAMPlaceFPGA else legalization and detailed placement are run using elfPlace |
dtype | float32 | data type, float32 (or) float64 |
plot_flag | 0 | whether to plot solution or not (Increases runtime) |
deterministic_flag | 1 | Ensures reproducible run-to-run results (Slightly increases runtime) |
To report a bug, please file an issue.
This software is released under a BSD 3-Clause "New" or "Revised" License. Please refer to LICENSE for details.