<?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 Traffic Bifurcation Between DPDK and Linux Kernel on LX2160ARDB Rev1 in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-on-LX2160ARDB/m-p/1245729#M10585</link>
    <description>&lt;P&gt;Hello everybody,&lt;/P&gt;&lt;P&gt;We are working on LX2160ARDB Rev1 board. The last version that LSDK supports LX2160ARDB Rev1 is 20.04, so we are using LSDK 20.04.&lt;/P&gt;&lt;P&gt;We are trying to use Linux network stack and DPDK applications both at the same time, Like shows in this example "&lt;A href="https://community.nxp.com/t5/QorIQ-Knowledge-Base/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-using-DPDMUX/ta-p/1124271" target="_blank"&gt;https://community.nxp.com/t5/QorIQ-Knowledge-Base/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-using-DPDMUX/ta-p/1124271&lt;/A&gt;"&lt;/P&gt;&lt;P&gt;When we follow the steps in example, the ldpdmux's link states are down. Therefore we can not ping to PC.&lt;/P&gt;&lt;P&gt;So, we decided to change described steps as compatible as our setup the appropriate way. We have only one connected port, it is board's DPMAC17.&lt;/P&gt;&lt;P&gt;Here is a two different approach we tried;&lt;/P&gt;&lt;P&gt;1. We created a DPDMUX. Uplink interface dpdmux.0.0 connected to DPMAC.17. Linux Kernel uses DPNI that connected to dpdmux.0.1. DPDK application uses DPNI that connected to dpdmux.0.2.&lt;/P&gt;&lt;P&gt;2. We created a DPSW. Uplink interface dpsw.0.0 connected to DPMAC.17. Linux Kernel uses DPNI that connected to dpsw.0.1. DPDK application uses DPNI that connected to dpsw.0.2.&lt;/P&gt;&lt;P&gt;After first approach;&lt;BR /&gt;DPDMUX interface's link states are up for DPNI3 (that using by kernel) and dpmac17 (that port connected).&lt;BR /&gt;DPNI2 (that using by DPDK) is down, because no DPDK app is running at this stage.&lt;BR /&gt;We gave ip addresses to eth2 but we couldnt ping to PC.&lt;/P&gt;&lt;P&gt;After second approach;&lt;BR /&gt;DPSW interface's link states are up for DPNI3 (that using by kernel) and dpmac17 (that port connected).&lt;BR /&gt;DPNI2 (that using by DPDK) is down, because no DPDK app is running at this stage.&lt;BR /&gt;We gave ip addresses to eth2 and we could ping to PC. But when we run a DPDK App(Even helloworld that not uses any Network Interface) we lost connection between Linux Kernel and PC.&lt;/P&gt;&lt;P&gt;Here are outputs for these approaches:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Traffic Bifurcation Between DPDK and Linux Kernel using DPDMUX.txt&lt;/LI&gt;&lt;LI&gt;Traffic Bifurcation Between DPDK and Linux Kernel using DPSW.txt&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;BR /&gt;My First question is; why we are not able ping to PC with DPDMUX approach?&lt;/P&gt;&lt;P&gt;Second one is; Why dpsw's link states are going down when we runs a DPDK App(Even helloworld that not uses any Network Interface) with DPSW approach?&lt;/P&gt;&lt;P&gt;Thank you all,&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Serhat&lt;/P&gt;</description>
    <pubDate>Mon, 15 Mar 2021 13:11:06 GMT</pubDate>
    <dc:creator>srtlkn</dc:creator>
    <dc:date>2021-03-15T13:11:06Z</dc:date>
    <item>
      <title>Traffic Bifurcation Between DPDK and Linux Kernel on LX2160ARDB Rev1</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-on-LX2160ARDB/m-p/1245729#M10585</link>
      <description>&lt;P&gt;Hello everybody,&lt;/P&gt;&lt;P&gt;We are working on LX2160ARDB Rev1 board. The last version that LSDK supports LX2160ARDB Rev1 is 20.04, so we are using LSDK 20.04.&lt;/P&gt;&lt;P&gt;We are trying to use Linux network stack and DPDK applications both at the same time, Like shows in this example "&lt;A href="https://community.nxp.com/t5/QorIQ-Knowledge-Base/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-using-DPDMUX/ta-p/1124271" target="_blank"&gt;https://community.nxp.com/t5/QorIQ-Knowledge-Base/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-using-DPDMUX/ta-p/1124271&lt;/A&gt;"&lt;/P&gt;&lt;P&gt;When we follow the steps in example, the ldpdmux's link states are down. Therefore we can not ping to PC.&lt;/P&gt;&lt;P&gt;So, we decided to change described steps as compatible as our setup the appropriate way. We have only one connected port, it is board's DPMAC17.&lt;/P&gt;&lt;P&gt;Here is a two different approach we tried;&lt;/P&gt;&lt;P&gt;1. We created a DPDMUX. Uplink interface dpdmux.0.0 connected to DPMAC.17. Linux Kernel uses DPNI that connected to dpdmux.0.1. DPDK application uses DPNI that connected to dpdmux.0.2.&lt;/P&gt;&lt;P&gt;2. We created a DPSW. Uplink interface dpsw.0.0 connected to DPMAC.17. Linux Kernel uses DPNI that connected to dpsw.0.1. DPDK application uses DPNI that connected to dpsw.0.2.&lt;/P&gt;&lt;P&gt;After first approach;&lt;BR /&gt;DPDMUX interface's link states are up for DPNI3 (that using by kernel) and dpmac17 (that port connected).&lt;BR /&gt;DPNI2 (that using by DPDK) is down, because no DPDK app is running at this stage.&lt;BR /&gt;We gave ip addresses to eth2 but we couldnt ping to PC.&lt;/P&gt;&lt;P&gt;After second approach;&lt;BR /&gt;DPSW interface's link states are up for DPNI3 (that using by kernel) and dpmac17 (that port connected).&lt;BR /&gt;DPNI2 (that using by DPDK) is down, because no DPDK app is running at this stage.&lt;BR /&gt;We gave ip addresses to eth2 and we could ping to PC. But when we run a DPDK App(Even helloworld that not uses any Network Interface) we lost connection between Linux Kernel and PC.&lt;/P&gt;&lt;P&gt;Here are outputs for these approaches:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Traffic Bifurcation Between DPDK and Linux Kernel using DPDMUX.txt&lt;/LI&gt;&lt;LI&gt;Traffic Bifurcation Between DPDK and Linux Kernel using DPSW.txt&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;BR /&gt;My First question is; why we are not able ping to PC with DPDMUX approach?&lt;/P&gt;&lt;P&gt;Second one is; Why dpsw's link states are going down when we runs a DPDK App(Even helloworld that not uses any Network Interface) with DPSW approach?&lt;/P&gt;&lt;P&gt;Thank you all,&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Serhat&lt;/P&gt;</description>
      <pubDate>Mon, 15 Mar 2021 13:11:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-on-LX2160ARDB/m-p/1245729#M10585</guid>
      <dc:creator>srtlkn</dc:creator>
      <dc:date>2021-03-15T13:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic Bifurcation Between DPDK and Linux Kernel on LX2160ARDB Rev1</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-on-LX2160ARDB/m-p/1265207#M10925</link>
      <description>&lt;P&gt;Please try with following&lt;/P&gt;
&lt;P&gt;1. Upgrade MC firmware to 10.25 or later&lt;/P&gt;
&lt;P&gt;2. Make sure you have following patches (assuming 4.19)&lt;/P&gt;
&lt;P&gt;&lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/commit/?h=linux-4.19&amp;amp;id=876b6662f2ffea3e35a692ff40e7469685b29c6b" target="_blank"&gt;https://source.codeaurora.org/external/qoriq/qoriq-components/linux/commit/?h=linux-4.19&amp;amp;id=876b6662f2ffea3e35a692ff40e7469685b29c6b&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://source.codeaurora.org/external/qoriq/qoriq-components/linux/commit/?h=linux-4.19-rt&amp;amp;id=63101cbb3c00dfe5d98628f7ff794e2c2f71d663" target="_blank"&gt;https://source.codeaurora.org/external/qoriq/qoriq-components/linux/commit/?h=linux-4.19-rt&amp;amp;id=63101cbb3c00dfe5d98628f7ff794e2c2f71d663&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Apr 2021 13:51:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Traffic-Bifurcation-Between-DPDK-and-Linux-Kernel-on-LX2160ARDB/m-p/1265207#M10925</guid>
      <dc:creator>hemantagrawal</dc:creator>
      <dc:date>2021-04-20T13:51:29Z</dc:date>
    </item>
  </channel>
</rss>

