Carmelo Cascone | f1d0a42 | 2017-09-07 17:21:46 +0200 | [diff] [blame^] | 1 | +---------------------------------------------------------------------+ |
| 2 | | Log file: mau.tp.log | |
| 3 | | Compiler version: 5.1.0 (fca32d1) | |
| 4 | | Created on: Thu Sep 7 14:49:38 2017 | |
| 5 | +---------------------------------------------------------------------+ |
| 6 | |
| 7 | ----- Stage 0 ------ |
| 8 | _condition_0 |
| 9 | ingress_pkt |
| 10 | ----- Stage 1 ------ |
| 11 | _condition_1 |
| 12 | table0 |
| 13 | ----- Stage 2 ------ |
| 14 | ecmp_group_table |
| 15 | ----- Stage 3 ------ |
| 16 | _condition_2 |
| 17 | ingress_port_count_table |
| 18 | egress_port_count_table |
| 19 | ----- Stage 0 ------ |
| 20 | _condition_3 |
| 21 | egress_pkt |
| 22 | ------------------------------------------ |
| 23 | Running Table Placement 4 |
| 24 | ------------------------------------------ |
| 25 | Cannot use hash action for table ingress_port_count_table. |
| 26 | Cannot use hash-action for table ingress_port_count_table with no key because the number of entries required by side-effect table ingress_port_counter is not a power of 2 -- 254. |
| 27 | Cannot use hash action for table egress_port_count_table. |
| 28 | Cannot use hash-action for table egress_port_count_table with no key because the number of entries required by side-effect table egress_port_counter is not a power of 2 -- 254. |
| 29 | Cannot use hash action for table ingress_pkt. |
| 30 | Table ingress_pkt has no side effect tables. |
| 31 | Cannot use hash action for table egress_pkt. |
| 32 | Table egress_pkt has no side effect tables. |
| 33 | User requested to not attempt to place action data parameters in the match overhead. |
| 34 | Cannot use hash action for table table0. |
| 35 | Cannot use hash-action for table table0 because it requires a ternary-style match for field ig_intr_md.ingress_port. |
| 36 | Cannot use hash action for table ecmp_group_table. |
| 37 | Cannot use hash-action for table ecmp_group_table because it has more than one side-effect table |
| 38 | ------------------------------------------ |
| 39 | Table Groups |
| 40 | ------------------------------------------ |
| 41 | Table Grouping (ingress) with match table ingress_port_count_table (1024) [ingress_port_count_table__action__ (1024), ingress_port_counter (254)] |
| 42 | Table Grouping (ingress) with match table egress_port_count_table (1024) [egress_port_count_table__action__ (1024), egress_port_counter (254)] |
| 43 | Table Grouping (ingress) with match table ingress_pkt (1024) [ingress_pkt__action__ (1024)] |
| 44 | Table Grouping (egress) with match table egress_pkt (1024) [egress_pkt__action__ (1024)] |
| 45 | Table Grouping (ingress) with match table table0 (512) [table0__action__ (512), table0_counter (512)] |
| 46 | Table Grouping (ingress) with match table ecmp_group_table (1024) [ecmp_group_table__action__ (1024), ecmp_group_table_counter (1024)] |
| 47 | Table Grouping (ingress) with condition table _condition_0 (0) [] |
| 48 | Table Grouping (ingress) with condition table _condition_1 (0) [] |
| 49 | Table Grouping (ingress) with condition table _condition_2 (0) [] |
| 50 | Table Grouping (egress) with condition table _condition_3 (0) [] |
| 51 | Phase 0 possible? False Cannot implement ingress_pkt in phase 0 resources because table does not have the correct condition |
| 52 | ------------------------------------ |
| 53 | Starting placement pass 0 |
| 54 | ------------------------------------ |
| 55 | |
| 56 | Nodes could place: |
| 57 | _condition_0 (2) |
| 58 | >> choose Table Grouping (ingress) with match table ingress_pkt (1024) [ingress_pkt__action__ (1024)] |
| 59 | Earliest stage can place: 0 |
| 60 | Placing table: ingress_pkt__action__ with 1024 entries |
| 61 | Table ingress_pkt__action__ with 0 entries is directly referenced |
| 62 | Match Table ingress_pkt has a total of 1 entries in stage 0 |
| 63 | Direct mapped table ingress_pkt__action__ has 0 entries |
| 64 | >> set ingress_pkt (9) to placed |
| 65 | >> set _condition_0 (2) to placed |
| 66 | |
| 67 | Nodes could place: |
| 68 | _condition_1 (3) |
| 69 | >> choose Table Grouping (ingress) with match table table0 (512) [table0__action__ (512), table0_counter (512)] |
| 70 | Earliest stage can place: 1 |
| 71 | Placing table: table0__action__ with 512 entries |
| 72 | Placing table: table0_counter with 512 entries |
| 73 | Table table0__action__ with 8192 entries is directly referenced |
| 74 | Table table0_counter with 4096 entries is directly referenced |
| 75 | Match Table table0 has a total of 512 entries in stage 1 |
| 76 | Direct mapped table table0__action__ has 8192 entries |
| 77 | Direct mapped table table0_counter has 4096 entries |
| 78 | >> set table0 (7) to placed |
| 79 | >> set _condition_1 (3) to placed |
| 80 | |
| 81 | Nodes could place: |
| 82 | ecmp_group_table (8) |
| 83 | >> choose Table Grouping (ingress) with match table ecmp_group_table (1024) [ecmp_group_table__action__ (1024), ecmp_group_table_counter (1024)] |
| 84 | Earliest stage can place: 2 |
| 85 | Placing table: ecmp_group_table__action__ with 1024 entries |
| 86 | Placing table: ecmp_group_table_counter with 1024 entries |
| 87 | Table ecmp_group_table__action__ with 0 entries is directly referenced |
| 88 | Table ecmp_group_table_counter with 4096 entries is directly referenced |
| 89 | Match Table ecmp_group_table has a total of 3072 entries in stage 2 |
| 90 | Direct mapped table ecmp_group_table__action__ has 0 entries |
| 91 | Direct mapped table ecmp_group_table_counter has 4096 entries |
| 92 | >> set ecmp_group_table (8) to placed |
| 93 | |
| 94 | Nodes could place: |
| 95 | _condition_2 (4) |
| 96 | >> choose Table Grouping (ingress) with match table ingress_port_count_table (1024) [ingress_port_count_table__action__ (1024), ingress_port_counter (254)] |
| 97 | Earliest stage can place: 3 |
| 98 | Placing table: ingress_port_count_table__action__ with 1024 entries |
| 99 | Placing table: ingress_port_counter with 254 entries |
| 100 | Table ingress_port_count_table__action__ with 0 entries is directly referenced |
| 101 | Table ingress_port_counter with 4096 entries is indirectly referenced |
| 102 | Match Table ingress_port_count_table has a total of 1 entries in stage 3 |
| 103 | Direct mapped table ingress_port_count_table__action__ has 0 entries |
| 104 | >> set ingress_port_count_table (5) to placed |
| 105 | >> set _condition_2 (4) to placed |
| 106 | |
| 107 | Nodes could place: |
| 108 | egress_port_count_table (6) |
| 109 | egress_port_count_table and _condition_2 not mutually exclusive |
| 110 | egress_port_count_table and ingress_port_count_table not mutually exclusive |
| 111 | >> choose Table Grouping (ingress) with match table egress_port_count_table (1024) [egress_port_count_table__action__ (1024), egress_port_counter (254)] |
| 112 | Earliest stage can place: 3 |
| 113 | egress_port_count_table and _condition_2 not mutually exclusive |
| 114 | egress_port_count_table and ingress_port_count_table not mutually exclusive |
| 115 | Placing table: egress_port_count_table__action__ with 1024 entries |
| 116 | Placing table: egress_port_counter with 254 entries |
| 117 | Table egress_port_count_table__action__ with 0 entries is directly referenced |
| 118 | Table egress_port_counter with 4096 entries is indirectly referenced |
| 119 | Match Table egress_port_count_table has a total of 1 entries in stage 3 |
| 120 | Direct mapped table egress_port_count_table__action__ has 0 entries |
| 121 | >> set egress_port_count_table (6) to placed |
| 122 | ------------------------------------ |
| 123 | Starting placement pass 1 |
| 124 | ------------------------------------ |
| 125 | |
| 126 | Nodes could place: |
| 127 | _condition_3 (2) |
| 128 | >> choose Table Grouping (egress) with match table egress_pkt (1024) [egress_pkt__action__ (1024)] |
| 129 | Earliest stage can place: 0 |
| 130 | Placing table: egress_pkt__action__ with 1024 entries |
| 131 | Table egress_pkt__action__ with 0 entries is directly referenced |
| 132 | Match Table egress_pkt has a total of 1 entries in stage 0 |
| 133 | Direct mapped table egress_pkt__action__ has 0 entries |
| 134 | >> set egress_pkt (3) to placed |
| 135 | >> set _condition_3 (2) to placed |
| 136 | |
| 137 | ------------------------------------------ |
| 138 | Logical Table IDs |
| 139 | ------------------------------------------ |
| 140 | Logical Table IDs in stage 0 are: |
| 141 | 0 : ingress_pkt |
| 142 | 1 : egress_pkt |
| 143 | Logical Table IDs in stage 1 are: |
| 144 | 0 : table0 |
| 145 | Logical Table IDs in stage 2 are: |
| 146 | 0 : ecmp_group_table |
| 147 | Logical Table IDs in stage 3 are: |
| 148 | 0 : ingress_port_count_table |
| 149 | 1 : egress_port_count_table |
| 150 | |
| 151 | ------------------------------------------ |
| 152 | |
| 153 | action mapping for ingress_port_count_table |
| 154 | count_ingress -> egress_port_count_table |
| 155 | action mapping for egress_port_count_table |
| 156 | count_egress -> --END_OF_PIPELINE-- |
| 157 | action mapping for ingress_pkt |
| 158 | _packet_out -> _condition_1 |
| 159 | action mapping for egress_pkt |
| 160 | add_packet_in_hdr -> --END_OF_PIPELINE-- |
| 161 | action mapping for table0 |
| 162 | set_egress_port -> _condition_2 |
| 163 | ecmp_group -> ecmp_group_table |
| 164 | send_to_cpu -> _condition_2 |
| 165 | _drop -> _condition_2 |
| 166 | action mapping for ecmp_group_table |
| 167 | set_egress_port -> _condition_2 |
| 168 | true/false mapping for _condition_0 |
| 169 | False -> _condition_1 |
| 170 | True -> ingress_pkt |
| 171 | true/false mapping for _condition_1 |
| 172 | False -> _condition_2 |
| 173 | True -> table0 |
| 174 | true/false mapping for _condition_2 |
| 175 | False -> --END_OF_PIPELINE-- |
| 176 | True -> ingress_port_count_table |
| 177 | true/false mapping for _condition_3 |
| 178 | False -> --END_OF_PIPELINE-- |
| 179 | True -> egress_pkt |