<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=koi8-r">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks for the explanation!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I understand your use case, and it cannot be supported with ConnectX-5.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Asaf Penso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Vladimir Yesin <v.yesin@gmail.com>
<br>
<b>Sent:</b> Tuesday, March 1, 2022 10:02 AM<br>
<b>To:</b> Asaf Penso <asafp@nvidia.com><br>
<b>Cc:</b> users@dpdk.org<br>
<b>Subject:</b> Re: Feature request: MLX5 DPDK flow item type RAW support<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hello Asaf,<o:p></o:p></p>
<div>
<p class="MsoNormal">I am currently working on forwarding IQ samples from EttusResearch USRP n320 SDR receiver to Nvidia GPU (via GPUDirect RDMA) with DPDK.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We are using Connectx-5 NICs.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">USRP uses CHDR network protocol (<a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffiles.ettus.com%2Fmanual_archive%2Frelease_003_009_000%2Fhtml%2Fpage_rtp.html&data=04%7C01%7Casafp%40nvidia.com%7Cf1ac28854ffa4ae872b008d9fb59bc44%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637817185558439757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BbSrEtZBIEfQkPU52Ed0A%2FGcwU8xC0CXrlAu4SSRL%2BY%3D&reserved=0">https://files.ettus.com/manual_archive/release_003_009_000/html/page_rtp.html</a>)
over UDP for CONTROL and DATA planes. CHDR is very similar to eCPRI, supported via DPDK flex item.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I am currently working on UHD driver (<a href="https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FEttusResearch%2Fuhd&data=04%7C01%7Casafp%40nvidia.com%7Cf1ac28854ffa4ae872b008d9fb59bc44%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637817185558439757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BCiDDWu6XTcbjQiTF3UsOPCWx75TQ7QXyEqj%2Bhtpz%2FY%3D&reserved=0">https://github.com/EttusResearch/uhd</a>) modification of
to split CONTROL and DATA plane CHDR flows to CPU and GPU respectively with DPDK flow API via distinct HW queues and mempools. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">CHDR header contains packet type field to separate these streams using RAW or FLEX items...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Currently, DPDK mlx5 PMD for Connectx-5 NICs does not implement flex and raw items.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The absence of these functions does not allow us to solve our problem.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">ÓÂ, 26 ÆÅ×Ò. 2022 Ç. × 21:08, Asaf Penso <<a href="mailto:asafp@nvidia.com">asafp@nvidia.com</a>>:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">Hello Vladimir,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Would you please elaborate more on your use case?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">What exactly do you wish to match on?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Currently, there is no plan to implement the RAW item.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">However, with Bluefield 2 DPU, we implemented the flex item, that can be useful for you.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="gmail-m_-4263199286418807856ms-outlook-mobile-signature">
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Asaf Penso<o:p></o:p></p>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="gmail-m_-4263199286418807856divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Vladimir Yesin <<a href="mailto:v.yesin@gmail.com" target="_blank">v.yesin@gmail.com</a>><br>
<b>Sent:</b> Friday, February 25, 2022 4:28:57 PM<br>
<b>To:</b> <a href="mailto:users@dpdk.org" target="_blank">users@dpdk.org</a> <<a href="mailto:users@dpdk.org" target="_blank">users@dpdk.org</a>><br>
<b>Subject:</b> Feature request: MLX5 DPDK flow item type RAW support</span> <o:p>
</o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p style="margin-top:0in"><span style="font-size:11.5pt;font-family:"Helvetica",sans-serif;color:#333333;letter-spacing:.1pt">Current DPDK 21.11 flow API does not support RTE_FLOW_ITEM_TYPE_RAW for MLX5.<o:p></o:p></span></p>
<p><span style="font-size:11.5pt;font-family:"Helvetica",sans-serif;color:#333333;letter-spacing:.1pt">I need support of RTE_FLOW_ITEM_TYPE_RAW in DPDK flow API to enqueue some ingress packets by content to GPU with support of GPUDirect RDMA and other to CPU
via distinct HW queues (RTE_FLOW_ACTION_TYPE_QUEUE).<o:p></o:p></span></p>
<p><span style="font-size:11.5pt;font-family:"Helvetica",sans-serif;color:#333333;letter-spacing:.1pt">For now RTE_FLOW_ITEM_TYPE_UDP and RTE_FLOW_ITEM_TYPE_IPV4 filtering and enqueueing with address and ports are supported.<o:p></o:p></span></p>
<p><span style="font-size:11.5pt;font-family:"Helvetica",sans-serif;color:#333333;letter-spacing:.1pt">Are there any plans to support RTE_FLOW_ITEM_TYPE_RAW for MLX5?<o:p></o:p></span></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>