-
Notifications
You must be signed in to change notification settings - Fork 12
/
hermes_glc_template.xml
414 lines (412 loc) · 25.7 KB
/
hermes_glc_template.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
<?xml version="1.0" ?>
<component id="root" name="root">
<component id="system" name="system">
<!--McPAT will skip the components if number is set to 0 -->
<param name="number_of_cores" value="1"/>
<param name="number_of_L1Directories" value="0"/>
<param name="number_of_L2Directories" value="0"/>
<param name="number_of_L2s" value="1"/> <!-- This number means how many L2 clusters in each cluster there can be multiple banks/ports -->
<param name="Private_L2" value="1"/><!--1 Private, 0 shared/coherent -->
<param name="number_of_L3s" value="1"/> <!-- This number means how many L3 clusters -->
<param name="number_of_NoCs" value="1"/>
<param name="homogeneous_cores" value="1"/><!--1 means homo -->
<param name="homogeneous_L2s" value="1"/>
<param name="homogeneous_L1Directories" value="0"/>
<param name="homogeneous_L2Directories" value="0"/>
<param name="homogeneous_L3s" value="1"/>
<param name="homogeneous_ccs" value="1"/><!--cache coherence hardware -->
<param name="homogeneous_NoCs" value="1"/>
<param name="core_tech_node" value="22"/><!-- nm -->
<param name="target_core_clockrate" value="3400"/><!--MHz -->
<param name="temperature" value="380"/> <!-- Kelvin -->
<param name="number_cache_levels" value="3"/>
<param name="interconnect_projection_type" value="0"/><!--0: aggressive wire technology; 1: conservative wire technology -->
<param name="device_type" value="0"/><!--0: HP(High Performance Type); 1: LSTP(Low standby power) 2: LOP (Low Operating Power) -->
<param name="longer_channel_device" value="1"/><!-- 0 no use; 1 use when possible -->
<param name="power_gating" value="1"/><!-- 0 not enabled; 1 enabled -->
<param name="machine_bits" value="64"/>
<param name="virtual_address_width" value="64"/>
<param name="physical_address_width" value="52"/>
<param name="virtual_memory_page_size" value="4096"/>
<!-- address width determines the tag_width in Cache, LSQ and buffers in cache controller
default value is machine_bits, if not set -->
<stat name="total_cycles" value="CS_SYSTEM_TOTAL_CYCLE"/>
<stat name="idle_cycles" value="CS_SYSTEM_IDLE_CYCLE"/>
<stat name="busy_cycles" value="CS_SYSTEM_BUSY_CYCLE"/>
<!--This page size(B) is complete different from the page size in Main memo section. this page size is the size of
virtual memory from OS/Archi perspective; the page size in Main memo section is the actual physical line in a DRAM bank -->
<!-- *********************** cores ******************* -->
<component id="system.core0" name="core0">
<!-- Core property -->
<param name="clock_rate" value="3400"/>
<param name="vdd" value="1.25"/><!-- 0 means using ITRS default vdd -->
<param name="power_gating_vcc" value="-1"/><!-- "-1" means using default power gating virtual power supply voltage constrained by technology and computed automatically -->
<param name="opt_local" value="0"/> <!-- for cores with unknown timing, set to 0 to force off the opt flag -->
<param name="instruction_length" value="32"/>
<param name="opcode_width" value="16"/>
<param name="x86" value="1"/>
<param name="micro_opcode_width" value="8"/>
<param name="machine_type" value="0"/>
<!-- inorder/OoO; 1 inorder; 0 OOO-->
<param name="number_hardware_threads" value="2"/>
<!-- number_instruction_fetch_ports(icache ports) is always 1 in single-thread processor,
it only may be more than one in SMT processors. BTB ports always equals to fetch ports since
branch information in consecutive branch instructions in the same fetch group can be read out from BTB once.-->
<param name="fetch_width" value="6"/> <!-- RBERA -->
<!-- fetch_width determines the size of cachelines of L1 cache block -->
<param name="number_instruction_fetch_ports" value="1"/>
<param name="decode_width" value="6"/> <!-- RBERA -->
<!-- decode_width determines the number of ports of the
renaming table (both RAM and CAM) scheme -->
<param name="issue_width" value="6"/> <!-- RBERA -->
<param name="peak_issue_width" value="6"/>
<!-- issue_width determines the number of ports of Issue window and other logic
as in the complexity effective processors paper; issue_width==dispatch_width -->
<param name="commit_width" value="6"/> <!-- RBERA -->
<!-- commit_width determines the number of ports of register files -->
<param name="fp_issue_width" value="2"/>
<param name="prediction_width" value="1"/>
<!-- number of branch instructions can be predicted simultaneously-->
<!-- Current version of McPAT does not distinguish int and floating point pipelines
Theses parameters are reserved for future use.-->
<param name="pipelines_per_core" value="1,1"/>
<!--integer_pipeline and floating_pipelines, if the floating_pipelines is 0, then the pipeline is shared-->
<param name="pipeline_depth" value="31,31"/>
<!-- pipeline depth of int and fp, if pipeline is shared, the second number is the average cycles of fp ops -->
<!-- issue and exe unit-->
<param name="ALU_per_core" value="6"/>
<!-- contains an adder, a shifter, and a logical unit -->
<param name="MUL_per_core" value="1"/>
<!-- For MUL and Div -->
<param name="FPU_per_core" value="2"/>
<!-- buffer between IF and ID stage -->
<param name="instruction_buffer_size" value="32"/>
<!-- buffer between ID and sche/exe stage -->
<param name="decoded_stream_buffer_size" value="16"/>
<param name="instruction_window_scheme" value="0"/><!-- 0 PHYREG based, 1 RSBASED-->
<!-- McPAT support 2 types of OoO cores, RS based and physical reg based-->
<param name="instruction_window_size" value="64"/>
<param name="fp_instruction_window_size" value="64"/>
<!-- the instruction issue Q as in Alpha 21264; The RS as in Intel P6 -->
<param name="ROB_size" value="512"/>
<!-- each in-flight instruction has an entry in ROB -->
<!-- registers -->
<param name="archi_Regs_IRF_size" value="16"/><!-- X86-64 has 16GPR -->
<param name="archi_Regs_FRF_size" value="32"/><!-- MMX + XMM -->
<!-- if OoO processor, phy_reg number is needed for renaming logic,
renaming logic is for both integer and floating point insts. -->
<param name="phy_Regs_IRF_size" value="256"/>
<param name="phy_Regs_FRF_size" value="256"/>
<!-- rename logic -->
<param name="rename_scheme" value="0"/>
<!-- can be RAM based(0) or CAM based(1) rename scheme
RAM-based scheme will have free list, status table;
CAM-based scheme have the valid bit in the data field of the CAM -->
<param name="checkpoint_depth" value="0"/>
<!-- RAM and CAM RAT contains checkpoints, checkpoint_depth=# of in_flight speculations;
RAM-based RAT should not have more than 4 GCs (e.g., MIPS R10000).
McPAT assumes the exsistance of RRAT when the RAM-RAT having no GCs (e.g., Netburst)
CAM-based RAT should have at least 1 GC and can have more than 8 GCs. -->
<param name="register_windows_size" value="0"/>
<!-- how many windows in the windowed register file, sun processors;
no register windowing is used when this number is 0 -->
<!-- In OoO cores, loads and stores can be issued whether inorder(Pentium Pro) or (OoO)out-of-order(Alpha),
They will always try to execute out-of-order though. -->
<param name="LSU_order" value="inorder"/>
<param name="store_buffer_size" value="96"/>
<!-- By default, in-order cores do not have load buffers -->
<param name="load_buffer_size" value="48"/>
<!-- number of ports refer to sustain-able concurrent memory accesses -->
<param name="memory_ports" value="3"/>
<!-- max_allowed_in_flight_memo_instructions determines the # of ports of load and store buffer
as well as the ports of Dcache which is connected to LSU -->
<!-- dual-pumped Dcache can be used to save the extra read/write ports -->
<param name="RAS_size" value="64"/>
<!-- general stats, defines simulation periods;require total, idle, and busy cycles for sanity check -->
<!-- please note: if target architecture is X86, then all the instructions refer to (fused) micro-ops -->
<stat name="total_instructions" value="CS_SYSTEM_CORE0_TOTAL_INSTRUCTIONS"/>
<stat name="int_instructions" value="CS_SYSTEM_CORE0_INT_INSTRUCTIONS"/>
<stat name="fp_instructions" value="CS_SYSTEM_CORE0_FP_INSTRUCTIONS"/>
<stat name="branch_instructions" value="CS_SYSTEM_CORE0_BRANCH_INSTRUCTIONS"/>
<stat name="branch_mispredictions" value="CS_SYSTEM_CORE0_BRANCH_MISPREDICTIONS"/>
<stat name="load_instructions" value="CS_SYSTEM_CORE0_LOAD_INSTRUCTIONS"/>
<stat name="store_instructions" value="CS_SYSTEM_CORE0_STORE_INSTRUCTIONS"/>
<stat name="committed_instructions" value="CS_SYSTEM_CORE0_COMMITTED_INSTRUCTIONS"/>
<stat name="committed_int_instructions" value="CS_SYSTEM_CORE0_COMMITTED_INT_INSUTRCTIONS"/>
<stat name="committed_fp_instructions" value="CS_SYSTEM_CORE0_COMMITTED_FP_INSTRUCTIONS"/>
<stat name="pipeline_duty_cycle" value="1"/><!--<=1, runtime_ipc/peak_ipc; averaged for all cores if homogeneous -->
<!-- the following cycle stats are used for heterogeneous cores only,
please ignore them if homogeneous cores -->
<stat name="total_cycles" value="CS_SYSTEM_CORE0_TOTAL_CYCLES"/>
<stat name="idle_cycles" value="CS_SYSTEM_CORE0_IDLE_CYCLES"/>
<stat name="busy_cycles" value="CS_SYSTEM_CORE0_BUSY_CYCLES"/>
<!-- instruction buffer stats -->
<!-- ROB stats, both RS and Phy based OoOs have ROB
performance simulator should capture the difference on accesses,
otherwise, McPAT has to guess based on number of committed instructions. -->
<stat name="ROB_reads" value="16"/>
<stat name="ROB_writes" value="16"/>
<!-- RAT accesses -->
<stat name="rename_reads" value="16"/> <!--lookup in renaming logic -->
<stat name="rename_writes" value="16"/><!--update dest regs. renaming logic -->
<stat name="fp_rename_reads" value="16"/>
<stat name="fp_rename_writes" value="16"/>
<!-- decode and rename stage use this, should be total ic - nop -->
<!-- Inst window stats -->
<stat name="inst_window_reads" value="16"/>
<stat name="inst_window_writes" value="16"/>
<stat name="inst_window_wakeup_accesses" value="16"/>
<stat name="fp_inst_window_reads" value="16"/>
<stat name="fp_inst_window_writes" value="16"/>
<stat name="fp_inst_window_wakeup_accesses" value="16"/>
<!-- RF accesses -->
<stat name="int_regfile_reads" value="16"/>
<stat name="float_regfile_reads" value="16"/>
<stat name="int_regfile_writes" value="16"/>
<stat name="float_regfile_writes" value="16"/>
<!-- accesses to the working reg -->
<stat name="function_calls" value="16"/>
<stat name="context_switches" value="16"/>
<!-- Number of Windows switches (number of function calls and returns)-->
<!-- Alu stats by default, the processor has one FPU that includes the divider and
multiplier. The fpu accesses should include accesses to multiplier and divider -->
<stat name="ialu_accesses" value="16"/>
<stat name="fpu_accesses" value="16"/>
<stat name="mul_accesses" value="16"/>
<stat name="cdb_alu_accesses" value="16"/>
<stat name="cdb_mul_accesses" value="16"/>
<stat name="cdb_fpu_accesses" value="16"/>
<!-- multiple cycle accesses should be counted multiple times,
otherwise, McPAT can use internal counter for different floating point instructions
to get final accesses. But that needs detailed info for floating point inst mix -->
<!-- currently the performance simulator should
make sure all the numbers are final numbers,
including the explicit read/write accesses,
and the implicit accesses such as replacements and etc.
Future versions of McPAT may be able to reason the implicit access
based on param and stats of last level cache
The same rule applies to all cache access stats too! -->
<!-- following is AF for max power computation.
Do not change them, unless you understand them-->
<stat name="IFU_duty_cycle" value="0.25"/> <!--depends on Icache line size and instruction issue rate -->
<stat name="LSU_duty_cycle" value="0.25"/>
<stat name="MemManU_I_duty_cycle" value="0.25"/>
<stat name="MemManU_D_duty_cycle" value="0.25"/>
<stat name="ALU_duty_cycle" value="1"/>
<stat name="MUL_duty_cycle" value="0.3"/>
<stat name="FPU_duty_cycle" value="0.3"/>
<stat name="ALU_cdb_duty_cycle" value="1"/>
<stat name="MUL_cdb_duty_cycle" value="0.3"/>
<stat name="FPU_cdb_duty_cycle" value="0.3"/>
<!-- ************** BRANCH PREDICTION UNIT ************** -->
<param name="number_of_BPT" value="2"/>
<component id="system.core0.predictor" name="PBT">
<!-- branch predictor; tournament predictor see Alpha implementation -->
<param name="local_predictor_size" value="10,3"/>
<param name="local_predictor_entries" value="1024"/>
<param name="global_predictor_entries" value="4096"/>
<param name="global_predictor_bits" value="2"/>
<param name="chooser_predictor_entries" value="4096"/>
<param name="chooser_predictor_bits" value="2"/>
<!-- These parameters can be combined like below in next version
<param name="load_predictor" value="10,3,1024"/>
<param name="global_predictor" value="4096,2"/>
<param name="predictor_chooser" value="4096,2"/>
-->
</component>
<param name="number_of_BTB" value="0"/>
<component id="system.core0.BTB" name="BTB">
<!-- all the buffer related are optional -->
<param name="BTB_config" value="5120,4,2,1, 1,3"/> <!--should be 4096 + 1024 -->
<!-- the parameters are capacity,block_width,associativity,bank, throughput w.r.t. core clock, latency w.r.t. core clock,-->
<stat name="read_accesses" value="16"/> <!--See IFU code for guideline -->
<stat name="write_accesses" value="16"/>
</component>
<!-- ************** MMU UNITS ************** -->
<component id="system.core0.itlb" name="itlb">
<param name="number_entries" value="256"/>
<stat name="total_accesses" value="16"/>
<stat name="total_misses" value="0"/>
<stat name="conflicts" value="0"/>
<!-- there is no write requests to itlb although writes happen to itlb after miss,
which is actually a replacement -->
</component>
<component id="system.core0.dtlb" name="dtlb">
<param name="number_entries" value="96"/><!--dual threads-->
<stat name="total_accesses" value="16"/>
<stat name="total_misses" value="0"/>
<stat name="conflicts" value="0"/>
</component>
<!-- ************** L1-I CACHE ************** -->
<component id="system.core0.icache" name="icache">
<!-- there is no write requests to itlb although writes happen to it after miss,
which is actually a replacement -->
<param name="icache_config" value="32768,64,8,1,8,4,64,1"/>
<!-- the parameters are capacity,block_width, associativity, bank, throughput w.r.t. core clock, latency w.r.t. core clock,output_width, cache policy, -->
<!-- cache_policy;//0 no write or write-though with non-write allocate;1 write-back with write-allocate -->
<param name="buffer_sizes" value="8,64,64,32"/>
<!-- cache controller buffer sizes: miss_buffer_size(MSHR),fill_buffer_size,prefetch_buffer_size,wb_buffer_size-->
<stat name="read_accesses" value="CS_SYSTEM_CORE0_ICACHE_READ_ACCESSES"/>
<stat name="read_misses" value="CS_SYSTEM_CORE0_ICACHE_READ_MISSES"/>
<stat name="conflicts" value="0"/>
</component>
<!-- ************** L1-D CACHE ************** -->
<component id="system.core0.dcache" name="dcache">
<!-- GLC's L1-D is actually 12 way. But for CACTI's sake, we assume it to be 8 ways -->
<param name="dcache_config" value="32768,64,8,1,8,5,64,1"/>
<!-- the parameters are capacity,block_width, associativity, bank, throughput w.r.t. core clock, latency w.r.t. core clock,output_width, cache policy, -->
<param name="buffer_sizes" value="16,64,8,64"/>
<!-- cache controller buffer sizes: miss_buffer_size(MSHR),fill_buffer_size,prefetch_buffer_size,wb_buffer_size-->
<stat name="read_accesses" value="CS_SYSTEM_CORE0_DCACHE_READ_ACCESSES"/>
<stat name="write_accesses" value="CS_SYSTEM_CORE0_DCACHE_WRITE_ACCESSES"/>
<stat name="read_misses" value="CS_SYSTEM_CORE0_DCACHE_READ_MISSES"/>
<stat name="write_misses" value="CS_SYSTEM_CORE0_DCACHE_WRITE_MISSES"/>
<stat name="conflicts" value="0"/>
</component>
</component>
<!-- ************** L2 DATA CACHE ************** -->
<component id="system.L20" name="L20">
<param name="L2_config" value="1310720,64,20,8,8,15,64,1"/>
<!-- the parameters are capacity,block_width, associativity, bank, throughput w.r.t. core clock, latency w.r.t. core clock,output_width, cache policy -->
<param name="buffer_sizes" value="48,48,16,48"/>
<!-- cache controller buffer sizes: miss_buffer_size(MSHR),fill_buffer_size,prefetch_buffer_size,wb_buffer_size-->
<param name="clockrate" value="3400"/>
<param name="vdd" value="0"/><!-- 0 means using ITRS default vdd -->
<param name="power_gating_vcc" value="-1"/><!-- "-1" means using default power gating virtual power supply voltage constrained by technology and computed automatically -->
<param name="ports" value="1,1,1"/>
<!-- number of r, w, and rw ports -->
<param name="device_type" value="0"/>
<stat name="read_accesses" value="CS_SYSTEM_L20_READ_ACCESSES"/>
<stat name="write_accesses" value="CS_SYSTEM_L20_WRITE_ACCESSES"/>
<stat name="read_misses" value="CS_SYSTEM_L20_READ_MISSES"/>
<stat name="write_misses" value="CS_SYSTEM_L20_WRITE_MISSES"/>
<stat name="conflicts" value="0"/>
<stat name="duty_cycle" value="0.5"/>
</component>
<!--**********************************************************************-->
<component id="system.L30" name="L30">
<param name="L3_config" value="3145728,64,12,16,16,55,64,1"/>
<!-- the parameters are capacity,block_width, associativity,bank, throughput w.r.t. core clock, latency w.r.t. core clock,-->
<param name="buffer_sizes" value="64,48,32,48"/>
<!-- cache controller buffer sizes: miss_buffer_size(MSHR),fill_buffer_size,prefetch_buffer_size,wb_buffer_size-->
<param name="clockrate" value="850"/>
<param name="ports" value="1,1,1"/>
<!-- number of r, w, and rw ports -->
<param name="device_type" value="0"/>
<param name="vdd" value="0"/><!-- 0 means using ITRS default vdd -->
<param name="power_gating_vcc" value="-1"/><!-- "-1" means using default power gating virtual power supply voltage constrained by technology and computed automatically -->
<stat name="read_accesses" value="CS_SYSTEM_L30_READ_ACCESSES"/>
<stat name="write_accesses" value="CS_SYSTEM_L30_WRITE_ACCESSES"/>
<stat name="read_misses" value="CS_SYSTEM_L30_READ_MISSES"/>
<stat name="write_misses" value="CS_SYSTEM_L30_WRITE_MISSES"/>
<stat name="conflicts" value="0"/>
<stat name="duty_cycle" value="1"/>
</component>
<!--**********************************************************************-->
<component id="system.NoC0" name="noc0">
<param name="clockrate" value="3400"/>
<param name="vdd" value="0"/><!-- 0 means using ITRS default vdd -->
<param name="power_gating_vcc" value="-1"/><!-- "-1" means using default power gating virtual power supply voltage constrained by technology and computed automatically -->
<param name="type" value="0"/>
<!--0:bus, 1:NoC , for bus no matter how many nodes sharing the bus
at each time only one node can send req -->
<param name="horizontal_nodes" value="1"/>
<param name="vertical_nodes" value="1"/>
<param name="has_global_link" value="0"/>
<!-- 1 has global link, 0 does not have global link -->
<param name="link_throughput" value="1"/><!--w.r.t clock -->
<param name="link_latency" value="1"/><!--w.r.t clock -->
<!-- throughput >= latency -->
<!-- Router architecture -->
<param name="input_ports" value="1"/>
<param name="output_ports" value="1"/>
<!-- For bus the I/O ports should be 1 -->
<param name="flit_bits" value="256"/>
<param name="chip_coverage" value="1"/>
<!-- When multiple NOC present, one NOC will cover part of the whole chip.
chip_coverage <=1 -->
<param name="link_routing_over_percentage" value="0.5"/>
<!-- Links can route over other components or occupy whole area.
by default, 50% of the NoC global links routes over other
components -->
<stat name="total_accesses" value="100000"/>
<!-- This is the number of total accesses within the whole network not for each router -->
<stat name="duty_cycle" value="1"/>
</component>
<!--**********************************************************************-->
<component id="system.mc" name="mc">
<!-- Memory controllers are for DDR(2,3...) DIMMs -->
<!-- current version of McPAT uses published values for base parameters of memory controller
improvements on MC will be added in later versions. -->
<param name="type" value="0"/> <!-- 1: low power; 0 high performance -->
<param name="mc_clock" value="200"/><!--DIMM IO bus clock rate MHz-->
<param name="vdd" value="0"/><!-- 0 means using ITRS default vdd -->
<param name="power_gating_vcc" value="-1"/><!-- "-1" means using default power gating virtual power supply voltage constrained by technology and computed automatically -->
<param name="peak_transfer_rate" value="3200"/><!--MB/S-->
<param name="block_size" value="64"/><!--B-->
<param name="number_mcs" value="0"/>
<!-- current McPAT only supports homogeneous memory controllers -->
<param name="memory_channels_per_mc" value="1"/>
<param name="number_ranks" value="1"/>
<param name="withPHY" value="0"/>
<!-- # of ranks of each channel-->
<param name="req_window_size_per_channel" value="32"/>
<param name="IO_buffer_size_per_channel" value="32"/>
<param name="databus_width" value="128"/>
<param name="addressbus_width" value="51"/>
<!-- McPAT will add the control bus width to the address bus width automatically -->
<stat name="memory_accesses" value="CS_SYSTEM_MC_MEMORY_ACCESSES"/>
<stat name="memory_reads" value="CS_SYSTEM_MC_MEMORY_READS"/>
<stat name="memory_writes" value="CS_SYSTEM_MC_MEMORY_WRITES"/>
<!-- McPAT does not track individual mc, instead, it takes the total accesses and calculate
the average power per MC or per channel. This is sufficient for most application.
Further track down can be easily added in later versions. -->
</component>
<!--**********************************************************************-->
<component id="system.niu" name="niu">
<!-- On chip 10Gb Ethernet NIC, including XAUI Phy and MAC controller -->
<!-- For a minimum IP packet size of 84B at 10Gb/s, a new packet arrives every 67.2ns.
the low bound of clock rate of a 10Gb MAC is 150Mhz -->
<param name="type" value="0"/> <!-- 1: low power; 0 high performance -->
<param name="clockrate" value="350"/>
<param name="vdd" value="0"/><!-- 0 means using ITRS default vdd -->
<param name="power_gating_vcc" value="-1"/><!-- "-1" means using default power gating virtual power supply voltage constrained by technology and computed automatically -->
<param name="number_units" value="0"/> <!-- unlike PCIe and memory controllers, each Ethernet controller only have one port -->
<stat name="duty_cycle" value="1.0"/> <!-- achievable max load <= 1.0 -->
<stat name="total_load_perc" value="0.7"/> <!-- ratio of total achieved load to total achieve-able bandwidth -->
<!-- McPAT does not track individual nic, instead, it takes the total accesses and calculate
the average power per nic or per channel. This is sufficient for most application. -->
</component>
<!--**********************************************************************-->
<component id="system.pcie" name="pcie">
<!-- On chip PCIe controller, including Phy-->
<!-- For a minimum PCIe packet size of 84B at 8Gb/s per lane (PCIe 3.0), a new packet arrives every 84ns.
the low bound of clock rate of a PCIe per lane logic is 120Mhz -->
<param name="type" value="0"/> <!-- 1: low power; 0 high performance -->
<param name="withPHY" value="1"/>
<param name="clockrate" value="350"/>
<param name="vdd" value="0"/><!-- 0 means using ITRS default vdd -->
<param name="power_gating_vcc" value="-1"/><!-- "-1" means using default power gating virtual power supply voltage constrained by technology and computed automatically -->
<param name="number_units" value="0"/>
<param name="num_channels" value="8"/> <!-- 2 ,4 ,8 ,16 ,32 -->
<stat name="duty_cycle" value="1.0"/> <!-- achievable max load <= 1.0 -->
<stat name="total_load_perc" value="0.7"/> <!-- Percentage of total achieved load to total achieve-able bandwidth -->
<!-- McPAT does not track individual pcie controllers, instead, it takes the total accesses and calculate
the average power per pcie controller or per channel. This is sufficient for most application. -->
</component>
<!--**********************************************************************-->
<component id="system.flashc" name="flashc">
<param name="number_flashcs" value="0"/>
<param name="type" value="1"/> <!-- 1: low power; 0 high performance -->
<param name="withPHY" value="1"/>
<param name="peak_transfer_rate" value="200"/><!--Per controller sustain-able peak rate MB/S -->
<param name="vdd" value="0"/><!-- 0 means using ITRS default vdd -->
<param name="power_gating_vcc" value="-1"/><!-- "-1" means using default power gating virtual power supply voltage constrained by technology and computed automatically -->
<stat name="duty_cycle" value="1.0"/> <!-- achievable max load <= 1.0 -->
<stat name="total_load_perc" value="0.7"/> <!-- Percentage of total achieved load to total achieve-able bandwidth -->
<!-- McPAT does not track individual flash controller, instead, it takes the total accesses and calculate
the average power per fc or per channel. This is sufficient for most application -->
</component>
<!--**********************************************************************-->
</component>
</component>