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 7840FA00C2; Thu, 3 Nov 2022 15:55:08 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0846542D16; Thu, 3 Nov 2022 15:55:04 +0100 (CET) Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) by mails.dpdk.org (Postfix) with ESMTP id A558940685 for ; Tue, 1 Nov 2022 03:30:34 +0100 (CET) Received: by mail-wr1-f54.google.com with SMTP id y16so18365009wrt.12 for ; Mon, 31 Oct 2022 19:30:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=31VzHo/ryS/L7w4us+L9XN7Ci2vySgLuDiGYn49qi8s=; b=ld669t4FIuzGDgF1oa9UDNCUZXfNDpw5/0i5da3ul2TK4FEKs7CHk1w3rLMUq+9UY4 E/3YkR9RAT8NDU/jfROkf37+3bpR+Ed32VCjjlEeJupdjyh3h7KFJG4oEPGy/fuwnU0c WuFhiuDou/Pv2wePmA2t4Gs2B73U2fEzqmDw4ROxTmQ4WSdla4t2JuajAeRK/K3tH2ut HtLJv377WzzmoLf0kljfFe4bu6RytFjeuxhwur65Wt72A2kSsx4oXTo4guM2fybwM4ZX DLNj7YmA7OHEXqOA+jRwcgRggl6eLeqEXqEqawCvJBm8wqFEZJLQZjPnPjpNhiaUQJL8 QCnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=31VzHo/ryS/L7w4us+L9XN7Ci2vySgLuDiGYn49qi8s=; b=kiFeUKI7dllWwhklQ+JI9eKuX34ij9DROLdgkIy0AZn0vRSGFUTzU0BUpb3y+hOAhv jul2k1VHKSb9EbbgS7ADOoqhls2nh2Aol2uOzxkRX86nkCRxwLHkfGblNw0PFn0u7wMQ +eyiNByiqXlcce8maGXw/PI3Toivv3/elP3v5r+0PZnxc7kS+5Pt9/hxgnJ2mSk44Yig 5Gso6OeIumrKf7rxow2VVZWOTz4Rx7R6oKkkKQR7kapxvDKC02vfs8wUSZGwB9Y4qo2j iY4CaqlmtXrhvRVwTy9BW+dkF2EnZUwS8EK0HLFcKRovaRggKVWthm0DNnZB2ng+ggPt Yd8A== X-Gm-Message-State: ACrzQf3SG+1naTa+zelikjlwr14HSilnGqRjOQxeQiU4ntvqKtokQYP9 Z7c5PsMG03bh9PkPNsLPaSW32eEM9/XCfnrko7A= X-Google-Smtp-Source: AMsMyM57xZ1x3bb1mgSUdEr2Lm4ZTwLP5TBMJJ/FNh8OXXv4S3SX2pzzKqcJTgoLy1MFTqlrywDVM7JzUTZF3uI0qrE= X-Received: by 2002:a5d:4887:0:b0:226:ed34:7bbd with SMTP id g7-20020a5d4887000000b00226ed347bbdmr9602595wrq.561.1667269833863; Mon, 31 Oct 2022 19:30:33 -0700 (PDT) MIME-Version: 1.0 References: <20221031171255.3e221d2c@shemminger-XPS-13-9360> In-Reply-To: <20221031171255.3e221d2c@shemminger-XPS-13-9360> From: Ramakrishnan G Date: Tue, 1 Nov 2022 08:00:22 +0530 Message-ID: Subject: Re: Flow Bifurcation of splitting the traffic between kernel space and user space (DPDK) To: stephen@networkplumber.org Cc: aaron.f.brown@intel.com, dev@dpdk.org, saravana3@gmail.com Content-Type: multipart/alternative; boundary="00000000000031384a05ec5f82b2" X-Mailman-Approved-At: Thu, 03 Nov 2022 15:55:02 +0100 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --00000000000031384a05ec5f82b2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear Stephan, Thanks for the quick response. Yes. we realised that the article is more than 5 years old. We thought that this code is part of kernel code. Our idea is to use the single NIC port and assign single IP Address like 16.10.56.78. If we access 16.10.56.78:9090, the traffic should be forwarded to kernel space by the XDP driver and all the other traffic should be sent to the user space (DPDK). I hope XDP driver is able to achieve this functionality. we will verify and update in this thread. Thanks, Ram On Tue, Nov 1, 2022 at 5:42 AM Stephen Hemminger wrote: > On Sat, 29 Oct 2022 02:39:01 +0530 > Ramakrishnan G wrote: > > > From: Ramakrishnan G > > To: aaron.f.brown@intel.com, dev@dpdk.org, saravana3@gmail.com > > Subject: Flow Bifurcation of splitting the traffic between kernel space > and user space (DPDK) > > Date: Sat, 29 Oct 2022 02:39:01 +0530 > > > > Dear Aaron and DPDK Dev Team, > > > > Thanks for the Article talks about the Traffic Flow bifurcation > > between kernel space and user space (DPDK) (3. Flow Bifurcation How-to > > Guide =E2=80=94 Data Plane Development Kit 16.07.2 documentation (dpdk.= org) > > ) > > That DPDK release is over 6 years old. That feature is no longer supporte= d > on Intel > NIC's. You are better off using AF_XDP. > > > > > We are trying to test this functionality for sending only the SSH (port > 22) > > traffic to kernel and all the other traffic to be transferred to the us= er > > space (DPDK) by assigning same IP for both the virtual interface (one > > virtual interface is owned by the DPDK and another virtual interface is > > owned by the DPDK ) > > > > Using the igb driver with max_vfs setting, we were able to create the > > virtual link and map it to user space (DPDK) and another link into kern= el > > space. we assigned different IP addresses and we were able to reach fro= m > > other host. > > > > But when we are trying to configure the flow-type for port 22 > > > > Ubuntu# ethtool -K eth9 ntuple on > > Ubuntu## ethtool -N eth9 flow-type ip4 dst-port 22 action 0 > > rmgr: Cannot insert RX class rule: Invalid argument > > Ubuntu## ethtool -N eth9 flow-type ip4 dst-port 22 action 1 > > rmgr: Cannot insert RX class rule: Invalid argument > > Ubuntu## ethtool -N eth9 flow-type ip4 dst-port 22 action 2 > > rmgr: Cannot insert RX class rule: Invalid argument > > > > We tried to apply the patch that was given in the following link, > > ( > > > https://patchwork.ozlabs.org/project/intel-wired-lan/patch/1451456399-133= 53-1-git-send-email-gangfeng.huang@ni.com/#1236040 > > ) > > > > But we couldn't patch any of the latest igb driver and we tried to patc= h > > with the 2016 igb driver. > > > > please help us in sharing the info where can we apply the patch for igb > > driver in Ubuntu. > > The igb NIC does not have an flow direction. > The bifurcation for Intel NIC is based off of kernel flow director. > --00000000000031384a05ec5f82b2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear Stephan,

Thanks for the quick=C2= =A0response. Yes. we realised that the article=C2=A0is more than 5 years ol= d. We thought that this code is part of kernel code.=C2=A0

Our idea is to use the single NIC port and assign single IP Addres= s like 16.10.56.78. If we access 16.10.= 56.78:9090, the traffic should be forwarded to kernel space by the XDP = driver and all the other traffic should be sent to the user space (DPDK). I= hope XDP driver is able to achieve this functionality. we will verify and = update in this thread.

Thanks,
Ram
=

= On Tue, Nov 1, 2022 at 5:42 AM Stephen Hemminger <stephen@networkplumber.org> wrote:
=
On Sat, 29 Oct 2022 02:39= :01 +0530
Ramakrishnan G <g= ramakr@gmail.com> wrote:

> From: Ramakrishnan G <gramakr@gmail.com>
> To: aaron= .f.brown@intel.com, d= ev@dpdk.org, s= aravana3@gmail.com
> Subject: Flow Bifurcation of splitting the traffic between kernel spac= e and=C2=A0 user space (DPDK)
> Date: Sat, 29 Oct 2022 02:39:01 +0530
>
> Dear Aaron and DPDK Dev Team,
>
> Thanks for the Article talks about the Traffic Flow bifurcation
> between kernel space and user space (DPDK) (3. Flow Bifurcation How-to=
> Guide =E2=80=94 Data Plane Development Kit 16.07.2 documentation (dpdk.org)<= br> > <https://doc.dpdk.org/guides-16= .07/howto/flow_bifurcation.html>)

That DPDK release is over 6 years old. That feature is no longer supported = on Intel
NIC's. You are better off using AF_XDP.

>
> We are trying to test this functionality for sending only the SSH (por= t 22)
> traffic to kernel and all the other traffic to be transferred to the u= ser
> space (DPDK) by assigning same IP for both the virtual interface (one<= br> > virtual interface is owned by the DPDK and another virtual interface i= s
> owned by the DPDK )
>
> Using the igb driver with max_vfs setting, we were able to create the<= br> > virtual link and map it to user space (DPDK) and another link into ker= nel
> space. we assigned different IP addresses and we were able to reach fr= om
> other host.
>
> But when we are trying to configure the flow-type for port 22
>
> Ubuntu# ethtool -K eth9 ntuple on
> Ubuntu## ethtool -N eth9 flow-type ip4 dst-port 22 action 0
> rmgr: Cannot insert RX class rule: Invalid argument
> Ubuntu## ethtool -N eth9 flow-type ip4 dst-port 22 action 1
> rmgr: Cannot insert RX class rule: Invalid argument
> Ubuntu## ethtool -N eth9 flow-type ip4 dst-port 22 action 2
> rmgr: Cannot insert RX class rule: Invalid argument
>
> We tried to apply the patch that was given in the following link,
> (
> https://patchwork.ozlabs.org/project/intel-wire= d-lan/patch/1451456399-13353-1-git-send-email-gangfeng.huang@ni.com/#123604= 0
> )
>
> But we couldn't patch any of the latest igb driver and we tried to= patch
> with the 2016 igb driver.
>
> please help us in sharing the info where can we apply the patch for ig= b
> driver in Ubuntu.

The igb NIC does not have an flow direction.
The bifurcation for Intel NIC is based off of kernel flow director.
--00000000000031384a05ec5f82b2--