From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 41CC7A034F for ; Tue, 1 Mar 2022 09:01:48 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 34D9B40E5A; Tue, 1 Mar 2022 09:01:48 +0100 (CET) Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) by mails.dpdk.org (Postfix) with ESMTP id CA48A407FF for ; Tue, 1 Mar 2022 09:01:46 +0100 (CET) Received: by mail-lj1-f177.google.com with SMTP id p20so20797588ljo.0 for ; Tue, 01 Mar 2022 00:01:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Mk5TN2VKyRNkP7E5tn6BiFjbE6bU6S6jWAGVhpwnGVg=; b=V5zN8ugJA2lEGn4FAHwWplgYy2dT2NZvNq0tjHMCIA/bksU+sTjyxMo5ufb2pjaWUg +6pv6rYYUlSCUsSs1gIKxFiLh0Vn0XY4D6f8CkWSrotoFfXztkFFE0kFX4enHU7AimnA +LKji7kFt8IulWjWAtwHmN+GndEjzBNFJzlGiOXIGNkTpe0j/Qd+XzNlCMY+YqotYFz0 2jHSIhIDmkRjvZNKl5w9QYKPzO2XOxYEIMstIfcNYnWsZd72pa3JBlllPnbFOpSzY0Ia wmOKQ2MKqp5HHZ5dWbsIYjG3QGQNV0isF6Zl5h7pR4dem17y/XHd9X0zcoX6uG0yAg6I hhWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Mk5TN2VKyRNkP7E5tn6BiFjbE6bU6S6jWAGVhpwnGVg=; b=yMgDj7/DiCsSPR0TJJn2whivmtZkNcF69pv8XBmKnjrzqBSJuOgZHXPHHhVd/HhvJ5 ZjFmg4Ciz6tBOtjV6Rr8C3vtzr9Wrk+06HGWhmPohkKYezKj8xN3ApmOEjd7lwZAM/Ru 6QSXWHDMvAGaJ6Lz6jGkGDbWnY/Olx6ZZnLMVIqbhfaeGAOIvcc6WIUUgrdZrpIi2akN Sf8EQdThycXd3sCiiWrRcnpQTOTZ46c8DlaQGvZKpUTbP8chlm4nuqucWlAayZSSHXcB i0dawztp8AKycWB9X7DYFVE4j6ghvI8PZAbGqrqgdSgYT2E7BjiBl6V6uFrKiI1EwGMm 6L2w== X-Gm-Message-State: AOAM533cGPbtg6LX6UCmssQL7IB534zajmkLz3e9m2L5RU6jBezEjO/X ihbFbwLqTYmVHECSC0pBuxPWRVC/SBFHp2ZxkV4= X-Google-Smtp-Source: ABdhPJw4LGcPJoS82+OYT+qUQY0pFhCxIPY/3B9PL5mSNvNX/rBXrjvYKSzsnHHzQfGuzYYjqiyXcSGj68kZoGATuH0= X-Received: by 2002:a2e:b712:0:b0:246:3ec4:7ed7 with SMTP id j18-20020a2eb712000000b002463ec47ed7mr16356734ljo.450.1646121705976; Tue, 01 Mar 2022 00:01:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Vladimir Yesin Date: Tue, 1 Mar 2022 11:01:34 +0300 Message-ID: Subject: Re: Feature request: MLX5 DPDK flow item type RAW support To: Asaf Penso Cc: "users@dpdk.org" Content-Type: multipart/alternative; boundary="0000000000008ab7cd05d9239377" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --0000000000008ab7cd05d9239377 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Asaf, I am currently working on forwarding IQ samples from EttusResearch USRP n320 SDR receiver to Nvidia GPU (via GPUDirect RDMA) with DPDK. We are using Connectx-5 NICs. USRP uses CHDR network protocol ( https://files.ettus.com/manual_archive/release_003_009_000/html/page_rtp.ht= ml) over UDP for CONTROL and DATA planes. CHDR is very similar to eCPRI, supported via DPDK flex item. I am currently working on UHD driver (https://github.com/EttusResearch/uhd) 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. CHDR header contains packet type field to separate these streams using RAW or FLEX items... Currently, DPDK mlx5 PMD for Connectx-5 NICs does not implement flex and raw items. The absence of these functions does not allow us to solve our problem. =D1=81=D0=B1, 26 =D1=84=D0=B5=D0=B2=D1=80. 2022 =D0=B3. =D0=B2 21:08, Asaf = Penso : > Hello Vladimir, > > Would you please elaborate more on your use case? > What exactly do you wish to match on? > > Currently, there is no plan to implement the RAW item. > However, with Bluefield 2 DPU, we implemented the flex item, that can be > useful for you. > > Regards, > Asaf Penso > ------------------------------ > *From:* Vladimir Yesin > *Sent:* Friday, February 25, 2022 4:28:57 PM > *To:* users@dpdk.org > *Subject:* Feature request: MLX5 DPDK flow item type RAW support > > > Current DPDK 21.11 flow API does not support RTE_FLOW_ITEM_TYPE_RAW for > MLX5. > > 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 othe= r > to CPU via distinct HW queues (RTE_FLOW_ACTION_TYPE_QUEUE). > > For now RTE_FLOW_ITEM_TYPE_UDP and RTE_FLOW_ITEM_TYPE_IPV4 filtering and > enqueueing with address and ports are supported. > > Are there any plans to support RTE_FLOW_ITEM_TYPE_RAW for MLX5? > --0000000000008ab7cd05d9239377 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Asaf,
I am currently working on forwarding IQ sa= mples from EttusResearch=C2=A0USRP n320 SDR receiver to Nvidia GPU (via GPU= Direct RDMA) with DPDK.
We are using Connectx-5 NICs.

USRP uses CHDR network protocol (https://f= iles.ettus.com/manual_archive/release_003_009_000/html/page_rtp.html) o= ver UDP for CONTROL and DATA planes. CHDR is very similar to eCPRI, support= ed via DPDK flex item.
I am currently working on UHD driver (https://github.com/EttusResear= ch/uhd)=C2=A0modification=C2=A0of to split CONTROL and DATA plane CHDR = flows to CPU and GPU respectively with DPDK flow API via distinct HW queues= and mempools.=C2=A0
CHDR header contains packet type field to se= parate these streams using RAW or FLEX items...

Cu= rrently, DPDK mlx5 PMD for Connectx-5 NICs does not implement flex and raw = items.
The absence of these functions does not allow us to solve = our problem.



=D1=81= =D0=B1, 26 =D1=84=D0=B5=D0=B2=D1=80. 2022 =D0=B3. =D0=B2 21:08, Asaf Penso = <asafp@nvidia.com>:
=
Hello Vladimir,

Would you please elaborate more on your use case?
What exactly do you wish to match on?

Currently, there is no plan to implement the RAW item.
However, with Bluefield 2 DPU, we implemented the flex it= em, that can be useful for you.

Regards,
Asaf Penso
Fro= m: Vladimir Yesin <v.yesin@gmail.com>
Sent: Friday, February 25, 2022 4:28:57 PM
To: users@dpdk.o= rg <users@dpdk.o= rg>
Subject: Feature request: MLX5 DPDK flow item type RAW support
=C2=A0

Current DPDK 21.11 flow API does not support RTE_FLOW_ITEM_TYPE_RAW for MLX= 5.

I need support of RTE_FLOW_ITEM_TYPE_RAW in DPDK flow API to enqueue some i= ngress packets by content to GPU with support of GPUDirect RDMA and other t= o CPU via distinct HW queues (RTE_FLOW_ACTION_TYPE_QUEUE).

For now RTE_FLOW_ITEM_TYPE_UDP and RTE_FLOW_ITEM_TYPE_IPV4 filtering and en= queueing with address and ports are supported.

Are there any plans to support RTE_FLOW_ITEM_TYPE_RAW for MLX5?

--0000000000008ab7cd05d9239377--