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 7FDF243C89; Mon, 11 Mar 2024 16:46:28 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 68FAB4067B; Mon, 11 Mar 2024 16:46:28 +0100 (CET) Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com [209.85.210.179]) by mails.dpdk.org (Postfix) with ESMTP id 657854027C for ; Mon, 11 Mar 2024 16:46:27 +0100 (CET) Received: by mail-pf1-f179.google.com with SMTP id d2e1a72fcca58-6e5eaf5bb3eso3466637b3a.3 for ; Mon, 11 Mar 2024 08:46:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1710171986; x=1710776786; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=fsdO7aBYJfSLlbChXYIILdz8rC5KUIeY6iUkMQUSfZw=; b=u66IteOJypE3BwvgBnoM06JJWuxNVFZPD/VEmFvYw1lhleFvE2qF9DZwL1avhSUu2E FZ7hKv05b4U3Gm/lK7FTU2f5i2cnJHgP0SbId0b53bXXi1XHYM2QoILMyHm/cS3qYTOm HoAYZcuP6oLJproE2vm1cJ/ues5cIskxWZ87rRs9MZRVzqbOslPRjdfiJgeeKI9adTJ8 Jn3btjo8xjKy6flLNXb0QBDiJ/9JR1Urh/cNPJWDfCChBFzjNcymJHTNv9mVeXjrLuH3 iT0tFx/58IGR91VcRNp4vpwtskNCTGjhY+QBYYYZymlmObEHHkjiQSMIMpvpOkyAYDFU 8wwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710171986; x=1710776786; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=fsdO7aBYJfSLlbChXYIILdz8rC5KUIeY6iUkMQUSfZw=; b=vyHDX8QF6YlhTsHmdTMrPWt8Q4UlNloeIHTmRFgqnZtVrJSneDJ1roE4i9FbDqN4TI Y0fPeBEdBxzW8gUnzi0+EYION3c4937mFWXIkdG5rffB5x0SAYyiIOxiduJ7mjLRjxCL j823Ppk3rAz6uld1pbdjojkDAy1eHZwbUpY9KuEQYNSgEFwuMtfjfZWh0t4D56hrv7+7 s05PLF5ERcgG7MyZs+iqM+ajiWoMb5b/TC2llZSNHskqYIuzPjSWx0i47Zq7+vJF4Zju bWfOfhbI/MoYu4yGEa3squMnyoPLP3dln3Ix+QV4DOBzfW7cJLmRG6xhu3XlyiQm90+Z hC0Q== X-Gm-Message-State: AOJu0Yw5u3PQC8HAz041GnbYoVjNAEM3vn8wVYrA12vKb7Tz3R+ONCU4 xv5xtbrA8UZH61v5XVQ0vWv2bsS3VN+sbtNtqfZLA25oWyPepFCj2gRvSSeRv5s= X-Google-Smtp-Source: AGHT+IF5SIl8pw1zh3rM06v8KGDZXYzU3w3C5bBK8zhY537LMbMLSmj872BLpXJ9jSlVP8xpo/xbYg== X-Received: by 2002:a05:6a20:158b:b0:1a1:8c67:25e1 with SMTP id h11-20020a056a20158b00b001a18c6725e1mr5096695pzj.45.1710171986415; Mon, 11 Mar 2024 08:46:26 -0700 (PDT) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id f13-20020a63dc4d000000b005dc8c301b9dsm4611559pgj.2.2024.03.11.08.46.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Mar 2024 08:46:26 -0700 (PDT) Date: Mon, 11 Mar 2024 08:46:24 -0700 From: Stephen Hemminger To: Balakrishnan K Cc: "dev@dpdk.org" , "users@dpdk.org" Subject: Re: is RSS and Flow director can work together Message-ID: <20240311084624.30cbbb63@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Mon, 11 Mar 2024 09:17:01 +0000 Balakrishnan K wrote: > Hi All, > I want to use the dpdk application with RSS and flow director. > is possible to use both at a time in application. > In RSS, I am using > action_rss_tcp.types = ETH_RSS_NONFRAG_IPV4_TCP | ETH_RSS_L3_SRC_ONLY | ETH_RSS_L3_DST_ONLY; > to receive the similar traffic to same core. > One specific case where I wanted to distribute the traffic across core, here the incoming traffic having same src and dst IP > Example( src ip : 10.10.10.1 dst ip :20.20.20.2) . > With RSS enabled all the traffic going to end up in one core ,where the remaining cores are being idle impacting the performance. > Planning enable flow director and create rule to distribute the traffic for the combination src /dst ip (10.10.10.1 /20.20.20.2) along with RSS. > > if RSS and flow rule having same criteria which one takes the priority . > > Regards, > Bala You can do that with rte_flow action of rte_flow_action_rss.