FPGA: Add note to large designs READMEs to warn users about large FPGA parts requirements (#1407)

Author: yuguen

DirectProgramming/C++SYCL_FPGA/ReferenceDesigns/crr/README.md

@@ -53,6 +53,8 @@ You can also find more information about [troubleshooting build errors](/DirectP
 >
 > :warning: Make sure you add the device files associated with the FPGA that you are targeting to your Intel® Quartus® Prime installation.
 
+> **Note**: You'll need a large FPGA part to be able to fit this design 
+
 ### Performance
 
 Performance results are based on testing as of July 20, 2020.

DirectProgramming/C++SYCL_FPGA/ReferenceDesigns/db/README.md

@@ -54,6 +54,8 @@ You can also find more information about [troubleshooting build errors](/DirectP
 >
 > :warning: Make sure you add the device files associated with the FPGA that you are targeting to your Intel® Quartus® Prime installation.
 
+> **Note**: You'll need a large FPGA part to be able to fit the query 9 variant of this design 
+
 ### Performance
 
 In this design, we accelerate four database queries as **offload accelerators**. In an offload accelerator scheme, the queries are performed by transferring the relevant data from the CPU host to the FPGA, starting the query kernel on the FPGA, and copying the results back. This means that the relevant performance number is the processing time (the wall clock time) from when the query is requested to the time the output data is accessible by the host. This includes the time to transfer data between the CPU and FPGA over PCIe (with an approximate read and write bandwidth of 6877 and 6582 MB/s, respectively). Most of the total query time is spent transferring the data between the CPU and FPGA, and the query kernels themselves are a small portion of the total latency.