Date: | Mon, 23 Apr 2007 17:13:46 -0500 (CDT) |
---|---|
From: | Mike Marty <mikem@xxxxxxxxxxx> |
Subject: | Re: [Gems-users] failed assertion 'id < m_nodes' |
There appears to be a limitation in the Ruby code that currently requires the number of Directory to be >= the number of chips. Probably fixable. See $gems/ruby/config/RubyConfig.[Ch] --Mike > Hi Mike, > > I sent the message several hours ago. Since it is not > listed on the mailing list, I'm sending it to you again. > > Here is my network file: > processors:8 > procs_per_chip:2 > L2banks:4 > memories:2 > bw_unit:10000 > > ext_node:L1Cache:0 int_node:0 link_latency:1 bw_multiplier:64 > ext_node:L1Cache:1 int_node:1 link_latency:1 bw_multiplier:64 > ext_node:L2Cache:0 int_node:3 link_latency:1 bw_multiplier:64 > ext_node:Directory:0 int_node:4 link_latency:20 bw_multiplier:10 > int_node:0 int_node:1 link_latency:1 bw_multiplier:16 > int_node:0 int_node:2 link_latency:1 bw_multiplier:16 > int_node:1 int_node:2 link_latency:1 bw_multiplier:16 > int_node:3 int_node:2 link_latency:4 bw_multiplier:16 > int_node:3 int_node:4 link_latency:20 bw_multiplier:10 > > ext_node:L1Cache:2 int_node:5 link_latency:1 bw_multiplier:64 > ext_node:L1Cache:3 int_node:6 link_latency:1 bw_multiplier:64 > ext_node:L2Cache:1 int_node:8 link_latency:1 bw_multiplier:64 > int_node:5 int_node:6 link_latency:1 bw_multiplier:16 > int_node:5 int_node:7 link_latency:1 bw_multiplier:16 > int_node:6 int_node:7 link_latency:1 bw_multiplier:16 > int_node:8 int_node:7 link_latency:4 bw_multiplier:16 > > int_node:3 int_node:4 link_latency:20 bw_multiplier:20 > int_node:8 int_node:4 link_latency:20 bw_multiplier:20 > > ext_node:L1Cache:4 int_node:10 link_latency:1 bw_multiplier:64 > ext_node:L1Cache:5 int_node:11 link_latency:1 bw_multiplier:64 > ext_node:L2Cache:2 int_node:13 link_latency:1 bw_multiplier:64 > ext_node:Directory:1 int_node:9 link_latency:20 bw_multiplier:10 > int_node:10 int_node:11 link_latency:1 bw_multiplier:16 > int_node:10 int_node:12 link_latency:1 bw_multiplier:16 > int_node:11 int_node:12 link_latency:1 bw_multiplier:16 > int_node:13 int_node:12 link_latency:4 bw_multiplier:16 > > ext_node:L1Cache:6 int_node:14 link_latency:1 bw_multiplier:64 > ext_node:L1Cache:7 int_node:15 link_latency:1 bw_multiplier:64 > ext_node:L2Cache:3 int_node:17 link_latency:1 bw_multiplier:64 > int_node:14 int_node:15 link_latency:1 bw_multiplier:16 > int_node:14 int_node:16 link_latency:1 bw_multiplier:16 > int_node:15 int_node:16 link_latency:1 bw_multiplier:16 > int_node:17 int_node:16 link_latency:4 bw_multiplier:16 > > int_node:13 int_node:9 link_latency:20 bw_multiplier:20 > int_node:17 int_node:9 link_latency:20 bw_multiplier:20 > > int_node:4 int_node:9 link_latency:40 bw_multiplier:40 > > |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] failed assertion 'id < m_nodes', Fengguang Song |
---|---|
Next by Date: | [Gems-users] LogTM Timestamp, James Wang |
Previous by Thread: | Re: [Gems-users] failed assertion 'id < m_nodes', Fengguang Song |
Next by Thread: | , (nil) |
Indexes: | [Date] [Thread] |