Hi,
I have DPAA2 user manual and I could not able to find the below features. Could you please provide whether LS1088A supports all the below features
The minimum throughput within the Ethernet layer shall be 1.5Gbps / 64byte packets with 802.1ad tagging being performed. |
Ethernet throughput shall be extensible, i.e. it should be possible to support higher throughput with minimal modification to software or network processing hardware. |
The minimum frame size shall be 64 bytes |
Jumbo frames, up to 9000 bytes (of payload) shall be supported |
Ethernet runt frames shall be dropped (a runt frame is less than 64 bytes) |
Any broken Ethernet frame (i.e. incomplete, incorrect CRC, etc.) shall also be dropped |
Ethernet latency shall be less than 10ms |
Ethernet latency should be less than 1ms |
Ethernet jitter shall be measured as Packet Delay Variation (PDV), as per ITU-T Recommendation Y.1540, section 6.2 |
Ethernet jitter shall be less than TODO – need to specify value |
PDV should also be calculated in accordance with RFC3393 |
Shall support: - 802.1D (Bridging & Spanning Tree) - 802.1Q (VLAN) - 802.1P (DSCP QOS) - 802.1ad (QinQ) |
Shall be transparent to L2CP frames |
Shal be transparent to IEEE 1588v2 and NTPv4 frames |
Shall support SyncE, this is encapsulated as; - ITU-T Rec. G.8261 that defines aspects about the architecture and the wander performance of SyncE networks - ITU-T Rec. G.8262 that specifies Synchronous Ethernet clocks for SyncE - ITU-T Rec. G.8264 that describes the specification of Ethernet Synchronization Messaging Channel (ESMC) |
All management traffic shall be IPv6 with an optional IPv4 interface |
The Access Point shall have a MAC table of at least 10k entries |
The RT should have a MAC table of at least 4k entries. |
Shall transparently carry: - 802.1D (Bridging & Spanning Tree) - 802.1Q (VLAN) - 802.1P (DSCP QOS) - 802.1ad (QinQ) |
Solved! Go to Solution.
The document you quoted doesn't appear to be originated by NXP. Please be aware,
that commenting documents of this kind is basically beyond the scope of NXP
Technical Support, especially when there are more than ten points to comment.
For the reasons mentioned above, only a very brief feedback can be provided:
The minimum throughput within the Ethernet layer shall be 1.5Gbps / 64byte
packets with 802.1ad tagging being performed.
Ethernet throughput shall be extensible, i.e. it should be possible to support
higher throughput with minimal modification to software or network processing
hardware.
DPAA2 switch is implemented in WRIOP which is a shared resource. The switching
throughput depends on the configuration and the set of tasks it executes.
Performance figures for certain usage scenarios may be available through distributors.
Contact your distributor for available performance and test reproducibility
information.
The minimum frame size shall be 64 bytes
Jumbo frames, up to 9000 bytes (of payload) shall be supported
Ethernet runt frames shall be dropped (a runt frame is less than 64 bytes)
Any broken Ethernet frame (i.e. incomplete, incorrect CRC, etc.) shall also be dropped
Supported
Ethernet latency shall be less than 10ms
Ethernet latency should be less than 1ms
Ethernet jitter shall be measured as Packet Delay Variation (PDV), as per ITU-T Recommendation Y.1540, section 6.2
Ethernet jitter shall be less than TODO – need to specify value
PDV should also be calculated in accordance with RFC3393
DPAA2 L2 Switch latency and jitter are not specified. WRIOP uses both internal
(on-chip) and externally connected memory to store frames. Thus, jitter and switching latency
depend on the configuration, load level introduced by the rest of the system and memory characteristics.
Shall be transparent to L2CP frames
The switch can be configured to pass or forward to the control port frames that
have destination MAC addresses reserved for control protocols.
Shal be transparent to IEEE 1588v2 and NTPv4 frames
DPAA2 L2 switch does not support time synchronization protocols and handles
frames that belong to them as ordinary frames.
hall support SyncE, this is encapsulated as;
- ITU-T Rec. G.8261 that defines aspects about the architecture and the wander performance of SyncE networks
- ITU-T Rec. G.8262 that specifies Synchronous Ethernet clocks for SyncE
- ITU-T Rec. G.8264 that describes the specification of Ethernet Synchronization Messaging Channel (ESMC)
There are no specific provisions for SyncE of any kind.
All management traffic shall be IPv6 with an optional IPv4 interface
The switch is controlled and configured by MC, it does not recognize or handle
any management traffic.
The Access Point shall have a MAC table of at least 10k entries
DPAA2 L2 switch is not a wireless access point.
The RT should have a MAC table of at least 4k entries.
Supported.
Shall transparently carry:
- 802.1D (Bridging & Spanning Tree)
See the note for L2CP above
- 802.1Q (VLAN)
Supported. There are multiple VLAN-related options, See DPAA2UM, Chapter 14
- 802.1P (DSCP QOS)
Supported. DPAA2UM, Section 14.3.27.
- 802.1ad (QinQ)
The switch recognizes and handles only the outmost VLAN tags. The rest is treated
as data.
Best Regards,
Platon
The document you quoted doesn't appear to be originated by NXP. Please be aware,
that commenting documents of this kind is basically beyond the scope of NXP
Technical Support, especially when there are more than ten points to comment.
For the reasons mentioned above, only a very brief feedback can be provided:
The minimum throughput within the Ethernet layer shall be 1.5Gbps / 64byte
packets with 802.1ad tagging being performed.
Ethernet throughput shall be extensible, i.e. it should be possible to support
higher throughput with minimal modification to software or network processing
hardware.
DPAA2 switch is implemented in WRIOP which is a shared resource. The switching
throughput depends on the configuration and the set of tasks it executes.
Performance figures for certain usage scenarios may be available through distributors.
Contact your distributor for available performance and test reproducibility
information.
The minimum frame size shall be 64 bytes
Jumbo frames, up to 9000 bytes (of payload) shall be supported
Ethernet runt frames shall be dropped (a runt frame is less than 64 bytes)
Any broken Ethernet frame (i.e. incomplete, incorrect CRC, etc.) shall also be dropped
Supported
Ethernet latency shall be less than 10ms
Ethernet latency should be less than 1ms
Ethernet jitter shall be measured as Packet Delay Variation (PDV), as per ITU-T Recommendation Y.1540, section 6.2
Ethernet jitter shall be less than TODO – need to specify value
PDV should also be calculated in accordance with RFC3393
DPAA2 L2 Switch latency and jitter are not specified. WRIOP uses both internal
(on-chip) and externally connected memory to store frames. Thus, jitter and switching latency
depend on the configuration, load level introduced by the rest of the system and memory characteristics.
Shall be transparent to L2CP frames
The switch can be configured to pass or forward to the control port frames that
have destination MAC addresses reserved for control protocols.
Shal be transparent to IEEE 1588v2 and NTPv4 frames
DPAA2 L2 switch does not support time synchronization protocols and handles
frames that belong to them as ordinary frames.
hall support SyncE, this is encapsulated as;
- ITU-T Rec. G.8261 that defines aspects about the architecture and the wander performance of SyncE networks
- ITU-T Rec. G.8262 that specifies Synchronous Ethernet clocks for SyncE
- ITU-T Rec. G.8264 that describes the specification of Ethernet Synchronization Messaging Channel (ESMC)
There are no specific provisions for SyncE of any kind.
All management traffic shall be IPv6 with an optional IPv4 interface
The switch is controlled and configured by MC, it does not recognize or handle
any management traffic.
The Access Point shall have a MAC table of at least 10k entries
DPAA2 L2 switch is not a wireless access point.
The RT should have a MAC table of at least 4k entries.
Supported.
Shall transparently carry:
- 802.1D (Bridging & Spanning Tree)
See the note for L2CP above
- 802.1Q (VLAN)
Supported. There are multiple VLAN-related options, See DPAA2UM, Chapter 14
- 802.1P (DSCP QOS)
Supported. DPAA2UM, Section 14.3.27.
- 802.1ad (QinQ)
The switch recognizes and handles only the outmost VLAN tags. The rest is treated
as data.
Best Regards,
Platon