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