<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>T-SeriesのトピックRe: T1040 L2 Switch high RX drop count on FMAN port</title>
    <link>https://community.nxp.com/t5/T-Series/T1040-L2-Switch-high-RX-drop-count-on-FMAN-port/m-p/674318#M2047</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A _jive_internal="true" data-content-finding="Community" data-userid="292938" data-username="elszymono" href="https://community.nxp.com/people/elszymono"&gt;Szymon Kukli,&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all, in Linux IP packet fragmentation is operated in L3(TCP/IP networking stack in Linux Kernel), the networking packet handled in L2switch is in L2(driver layer).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Port8 and Port 9 in L2switch are 2.5G SGMII ports connecting to FMAN. In l2switch-util application, the Maximum frame length is configured as 10240.&lt;/P&gt;&lt;P&gt;Please refer to the following in the file include/vtss_api/vtss_port_api.h of l2switch package.&lt;/P&gt;&lt;P&gt;#define VTSS_MAX_FRAME_LENGTH_MAX&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10240&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So please enlarge the variable VTSS_MAX_FRAME_LENGTH_MAX to make it support your networking environment.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 Jul 2017 12:01:06 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2017-07-05T12:01:06Z</dc:date>
    <item>
      <title>T1040 L2 Switch high RX drop count on FMAN port</title>
      <link>https://community.nxp.com/t5/T-Series/T1040-L2-Switch-high-RX-drop-count-on-FMAN-port/m-p/674317#M2046</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're working on a solution, where we hook the T1040 integrated switch to a number of different switches/processors (including the LS1021 and another T1040).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, whenever we start sending a sequence of 65kB IPv4|IPv6 packets (which are fragmented to 1500B Ethernet frames) from the T1040 and any other port simultaneously, we observe a significant RX drop count on the integrated switch interface connected to the T1040 FMAN (chip_port 8 on VSC9953).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue doesn't show up on any other of the T1040 ports (tested on chip_ports 0, 1, 2, 3). When we connect two T1040 through the switch ports and we run the ping (-f -s65000) from both sides, we experience the issue symmetrically on both (we see large RX drop increase on the internal switch port connected to the T1040 FMAN - rmon.rx_etherStatsFragments in vtss_port_counters_t struct increase on chip_ports 8 on both T1040s).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This problem occurs when we use the reference application from NXP (l2switch-util) with l2switch-uio kernel driver. It seems there is a fundamental problem in T1040 FMAN &amp;lt;-&amp;gt; integrated switch connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jun 2017 22:44:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T1040-L2-Switch-high-RX-drop-count-on-FMAN-port/m-p/674317#M2046</guid>
      <dc:creator>elszymono</dc:creator>
      <dc:date>2017-06-26T22:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: T1040 L2 Switch high RX drop count on FMAN port</title>
      <link>https://community.nxp.com/t5/T-Series/T1040-L2-Switch-high-RX-drop-count-on-FMAN-port/m-p/674318#M2047</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A _jive_internal="true" data-content-finding="Community" data-userid="292938" data-username="elszymono" href="https://community.nxp.com/people/elszymono"&gt;Szymon Kukli,&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all, in Linux IP packet fragmentation is operated in L3(TCP/IP networking stack in Linux Kernel), the networking packet handled in L2switch is in L2(driver layer).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Port8 and Port 9 in L2switch are 2.5G SGMII ports connecting to FMAN. In l2switch-util application, the Maximum frame length is configured as 10240.&lt;/P&gt;&lt;P&gt;Please refer to the following in the file include/vtss_api/vtss_port_api.h of l2switch package.&lt;/P&gt;&lt;P&gt;#define VTSS_MAX_FRAME_LENGTH_MAX&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10240&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So please enlarge the variable VTSS_MAX_FRAME_LENGTH_MAX to make it support your networking environment.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jul 2017 12:01:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T1040-L2-Switch-high-RX-drop-count-on-FMAN-port/m-p/674318#M2047</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2017-07-05T12:01:06Z</dc:date>
    </item>
  </channel>
</rss>

