<?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 DPAA2 frames segmentation in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/DPAA2-frames-segmentation/m-p/1548250#M11358</link>
    <description>&lt;P&gt;According to the DPAA2 Low-Level Hardware Reference Manual (screenshot attached), a single frame can carry up to 4GiB-1 bytes. It's significantly larger then widely used MTUs. Does it mean that such huge frames with TCP packets will be segmented at the WRIOP level?&lt;/P&gt;</description>
    <pubDate>Thu, 03 Nov 2022 10:36:13 GMT</pubDate>
    <dc:creator>dsl</dc:creator>
    <dc:date>2022-11-03T10:36:13Z</dc:date>
    <item>
      <title>DPAA2 frames segmentation</title>
      <link>https://community.nxp.com/t5/Layerscape/DPAA2-frames-segmentation/m-p/1548250#M11358</link>
      <description>&lt;P&gt;According to the DPAA2 Low-Level Hardware Reference Manual (screenshot attached), a single frame can carry up to 4GiB-1 bytes. It's significantly larger then widely used MTUs. Does it mean that such huge frames with TCP packets will be segmented at the WRIOP level?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 10:36:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/DPAA2-frames-segmentation/m-p/1548250#M11358</guid>
      <dc:creator>dsl</dc:creator>
      <dc:date>2022-11-03T10:36:13Z</dc:date>
    </item>
  </channel>
</rss>

