<?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>topic Queue Allocation Limitations on LX2160A Custom Board with Multiple Ethernet Interfaces in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/Queue-Allocation-Limitations-on-LX2160A-Custom-Board-with/m-p/1995943#M15106</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Hardware:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;CPU:&lt;/STRONG&gt; LX2160A&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Board:&lt;/STRONG&gt; Custom board with 16 1000BaseX SFP Ethernet ports (DPMAC3-DPMAC18)&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;SerDes1 Protocol:&lt;/STRONG&gt; 4 (8x 1G Ethernet)&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;SerDes2 Protocol:&lt;/STRONG&gt; 9 (8x 1G Ethernet)&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;SerDes3 Protocol:&lt;/STRONG&gt; 3 (2x PCIe)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Software:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Bootloaders and Linux firmware are based on "LSDK-21.08" branches&lt;/LI&gt;&lt;LI&gt;MC Firmware Version: v10.39.0&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We have attached a diagram illustrating our DPL configuration, as well as the DPL DTS file obtained using the command restool dprc generate-dpl dprc.1 for a setup with 12 queues per interface.&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;&lt;STRONG&gt;Issue Description:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;We can successfully allocate 8 queues (1 traffic class) for each of the 16 interfaces (DPMAC3-DPMAC18) without issues. However, when attempting to allocate 12 queues (1 traffic class) per interface, we receive the following error messages in the MC log:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;[E, allocate_resource:1114] resman_bind() failed for DCP-8WQ&lt;BR /&gt;[E, allocate_channel_resources:168, DPCON] Ignore above error message, continue with 8WQ channel allocation...&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;Despite these errors, all ports appear to work correctly.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Questions:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is it safe to use this configuration with 12 queues per interface, or do the error messages indicate a potential problem?&lt;/LI&gt;&lt;LI&gt;If there is an issue, can you suggest a way to resolve it?&lt;/LI&gt;&lt;/OL&gt;&lt;HR /&gt;&lt;P&gt;When attempting to allocate even more queues (14 or 16 per interface), we encounter "No resources" errors, resulting in the failure to create some interfaces:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.18&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.17&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.16&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.15&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.14&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.13&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.12&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.11&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.10&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.9&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.8&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.7&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.6&lt;/P&gt;&lt;P&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.5&lt;BR /&gt;MC error: No resources (status 0x8)&lt;BR /&gt;Error: dpcon object was not created!&lt;/P&gt;&lt;P&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.4&lt;BR /&gt;MC error: No resources (status 0x8)&lt;BR /&gt;Error: dpcon object was not created!&lt;/P&gt;&lt;P&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.3&lt;BR /&gt;MC error: No resources (status 0x8)&lt;BR /&gt;Error: dpcon object was not created!&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;STRONG&gt;Further Questions:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;What is the maximum number of queues we can allocate for all 16 interfaces?&lt;/LI&gt;&lt;LI&gt;Is there a specific limit on queue allocation, and is it possible to increase this limit to allocate more queues per interface?&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Mon, 18 Nov 2024 03:24:33 GMT</pubDate>
    <dc:creator>o_m_v</dc:creator>
    <dc:date>2024-11-18T03:24:33Z</dc:date>
    <item>
      <title>Queue Allocation Limitations on LX2160A Custom Board with Multiple Ethernet Interfaces</title>
      <link>https://community.nxp.com/t5/Layerscape/Queue-Allocation-Limitations-on-LX2160A-Custom-Board-with/m-p/1995943#M15106</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hardware:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;CPU:&lt;/STRONG&gt; LX2160A&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Board:&lt;/STRONG&gt; Custom board with 16 1000BaseX SFP Ethernet ports (DPMAC3-DPMAC18)&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;SerDes1 Protocol:&lt;/STRONG&gt; 4 (8x 1G Ethernet)&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;SerDes2 Protocol:&lt;/STRONG&gt; 9 (8x 1G Ethernet)&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;SerDes3 Protocol:&lt;/STRONG&gt; 3 (2x PCIe)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Software:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Bootloaders and Linux firmware are based on "LSDK-21.08" branches&lt;/LI&gt;&lt;LI&gt;MC Firmware Version: v10.39.0&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We have attached a diagram illustrating our DPL configuration, as well as the DPL DTS file obtained using the command restool dprc generate-dpl dprc.1 for a setup with 12 queues per interface.&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;&lt;STRONG&gt;Issue Description:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;We can successfully allocate 8 queues (1 traffic class) for each of the 16 interfaces (DPMAC3-DPMAC18) without issues. However, when attempting to allocate 12 queues (1 traffic class) per interface, we receive the following error messages in the MC log:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;[E, allocate_resource:1114] resman_bind() failed for DCP-8WQ&lt;BR /&gt;[E, allocate_channel_resources:168, DPCON] Ignore above error message, continue with 8WQ channel allocation...&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;Despite these errors, all ports appear to work correctly.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Questions:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is it safe to use this configuration with 12 queues per interface, or do the error messages indicate a potential problem?&lt;/LI&gt;&lt;LI&gt;If there is an issue, can you suggest a way to resolve it?&lt;/LI&gt;&lt;/OL&gt;&lt;HR /&gt;&lt;P&gt;When attempting to allocate even more queues (14 or 16 per interface), we encounter "No resources" errors, resulting in the failure to create some interfaces:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.18&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.17&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.16&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.15&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.14&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.13&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.12&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.11&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.10&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.9&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.8&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.7&lt;BR /&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.6&lt;/P&gt;&lt;P&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.5&lt;BR /&gt;MC error: No resources (status 0x8)&lt;BR /&gt;Error: dpcon object was not created!&lt;/P&gt;&lt;P&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.4&lt;BR /&gt;MC error: No resources (status 0x8)&lt;BR /&gt;Error: dpcon object was not created!&lt;/P&gt;&lt;P&gt;root@TinyLinux:~# ls-addni -nq=16 -t=1 dpmac.3&lt;BR /&gt;MC error: No resources (status 0x8)&lt;BR /&gt;Error: dpcon object was not created!&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;STRONG&gt;Further Questions:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;What is the maximum number of queues we can allocate for all 16 interfaces?&lt;/LI&gt;&lt;LI&gt;Is there a specific limit on queue allocation, and is it possible to increase this limit to allocate more queues per interface?&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Mon, 18 Nov 2024 03:24:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Queue-Allocation-Limitations-on-LX2160A-Custom-Board-with/m-p/1995943#M15106</guid>
      <dc:creator>o_m_v</dc:creator>
      <dc:date>2024-11-18T03:24:33Z</dc:date>
    </item>
    <item>
      <title>Re: Queue Allocation Limitations on LX2160A Custom Board with Multiple Ethernet Interfaces</title>
      <link>https://community.nxp.com/t5/Layerscape/Queue-Allocation-Limitations-on-LX2160A-Custom-Board-with/m-p/1995944#M15107</link>
      <description />
      <pubDate>Mon, 18 Nov 2024 03:26:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Queue-Allocation-Limitations-on-LX2160A-Custom-Board-with/m-p/1995944#M15107</guid>
      <dc:creator>o_m_v</dc:creator>
      <dc:date>2024-11-18T03:26:54Z</dc:date>
    </item>
    <item>
      <title>Re: Queue Allocation Limitations on LX2160A Custom Board with Multiple Ethernet Interfaces</title>
      <link>https://community.nxp.com/t5/Layerscape/Queue-Allocation-Limitations-on-LX2160A-Custom-Board-with/m-p/1999885#M15118</link>
      <description>&lt;P&gt;&lt;SPAN&gt;For this case, suggest modifying the DPC DTS as below, &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - wq_ch_conversion = &amp;lt;32&amp;gt;;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;+ wq_ch_conversion = &amp;lt;64&amp;gt;;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Refer to the following note from this section 8.3.2.3.3.1 DPAA2 objects dependencies in LSDKUG2108.pdf.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Note that DPIO objects themselves transparently consume DPCONs (one&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;per DPIO object), which therefore must be subtracted from the total&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;number available to the DPNIs (they need not be explicitly declared in&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;the DPL, but they are simply not available to the rest of the system).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The system can provide up to 64 8-WQ DPCONs (and up to 256&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2-WQ DPCONs and combinations thereof).&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 07:59:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Queue-Allocation-Limitations-on-LX2160A-Custom-Board-with/m-p/1999885#M15118</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2024-11-22T07:59:27Z</dc:date>
    </item>
  </channel>
</rss>

