at some level the system closes, eg. Workstation, PDA, etc.
2.2 Wiring Requirements
-
-
-
- If wires are the limited resource, Area is
- If wires are the limited resource, Area per LUT is
, p > 0.5
3.0 Switches
Consider a specific structure built according to the Rent's rule.
Fig. 3.1 Model hierarchical architecture
This is a fully hierarchical interconnect with the following properties
- inter-level signaling bandwidth growing according to Rent's rule
- for simplicity only unidirectional signal wires are considered
- gates recursively partitioned into n equally sized sets at
each level of hierarchy
- principal interconnect occurs at each node of convergence in the
hierarchy
- at any level l in the hierarchy, each node has a fan-in from
below of
signals and a fan-in from above of
From this the total number of switches can be calculated to give,
further math (see thesis) gives,
If switches are the limited resource,
Fig. 3.2 Switches and Wires, direct calculation
Fig. 3.3 Switches and Wires, direct calculation
(same as Fig. 3.2, but zoomed in to see p=0.5 better)
4.0 Switches and Wires
p < 0.5, Asymptotic Area per LUT is O(1)
p > 0.5, Asymptotic Area per LUT is
For p > 0.5 interconnect dominates. Note that the switching
growth shown is the minimum required to route graphs for a given p.
It is possible to construct architectures with BW and switching growth
as shown to route any graph with
5.0 Shortcomings of Rent's Rule
Eventhough Rent's rule estimates the number of wires and switches
required to find a route, it is purely based on geometry, it does
not consider the criical path. A partition can result in the critical
path weaving between the halves. This is partly the reason why we see
p~0.75 for high speed logic, while general logic has p~0.5.
Fig. 5.1 illustrates this point. The left side is partitioned
for minimum wires crossing halves. This results in the critcal
path crossing the partition twice. In the figure on the right, the
design has been reorganized to contain the critical path on one
half, at the cost of a larger cut size between the halves.
Fig. 5.1 Partitioning based on critical path length
6.0 Efficiency
Let, is the designed net resource, and
is the number from Rent's rule.
What happens when
?
Wastage of routing resource.
?
The LUTs have to be under-utilized by C so that routing is possible
Figures below show the relative overheads for implementing
designs with
on
designs.
Fig. 6.1 Efficiency - Discrete
Fig. 6.2 Efficiency - Continuous
Figure below plots the continuous case in three axes
Fig. 6.3 Efficiency - Continuous
The network connectivity can be picked if we assume the typical
designs will have a uniform .
From this the expected overhead can be calculated. Figure below
gives the expected overhead for
uniformly distributed
between 0.4 <= <=0.8.
Fig. 6.4 Expected Overhead
7.0 Sea of Gates
Once the interconnect dominates and one expects a range of p's
for subcomponents, focus on using the interconnect.
Fig. 7.1 The Sea-of-Gates concept
If most of the interconnect resources are usable as needed (not dedicated
to a LUT), it does not hurt to have gates which you ignore when p
is high.
8.0 Summary
- cannot afford full interconnect
- cannot make all interconnects local
- Rent's rule captures typical locality/structure in nets
- Rent parameter varies among computing structures
- interconnect resources grow as
- too much interconnect can be just as inefficient as too little
- demanding full routability of all designs hurts you in area
- time for a Sea-of-gates philosophy for FPGAs ?