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 956794619F for ; Wed, 5 Feb 2025 17:50:01 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 42A5840270; Wed, 5 Feb 2025 17:50:01 +0100 (CET) Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) by mails.dpdk.org (Postfix) with ESMTP id A8C0940261 for ; Wed, 5 Feb 2025 17:50:00 +0100 (CET) Received: by mail-pl1-f178.google.com with SMTP id d9443c01a7336-21f237fb0eeso222245ad.2 for ; Wed, 05 Feb 2025 08:50:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1738774199; x=1739378999; 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=pDHv753VwbgTwmripqL2GyUbTQn/6X6wT4UDoaLEXAI=; b=sDzy5aqiLTxrX9krxSg27rJPfZm3+Zk6TLvw0vMENZxbEigpQNhzcxGc71Ts+Dh9Om T4tzyjUP8uoexLzTM2iAy5BlCdKBRdkedHM/OrKSPBxN6FPE4LHEImS2VzR7iA3X1wHt wPgLFiVa5I908hfGdUxwv9TvgCfUPQ+YINVwxEA825APmkUgmHV8z3+uVdrC5ESvpZS4 GRLx4jcs198ycVqlxMh+4/pWX68ClG1OX2WQcQm6vq6a0iR6tOP2CSmBbLLPiC7MasmZ 7PX6mv6JWK4UnEmggXghLr14vQj5zFGic7h2wV/8KexP0dTAPdm0lgoVXVGx/3VXHe0f tEKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738774199; x=1739378999; 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=pDHv753VwbgTwmripqL2GyUbTQn/6X6wT4UDoaLEXAI=; b=WTCC/IILs4fpG+42dfpLaBpiVT5ragdT0TWzTRy49I1r40yTqqLkWFUkbK+wYuDF6C oZ2YuyMxY0bHLLpvoyfc8Kcf0IdL4HMSC79TdN6UmAat5rqxmF3nAT0EOgcFwGzj+/JT FYwPxSSLd/UTgLFo3dZX4S27SoVWFOnd+lgW7ZHozwWccyYa3xdAV8Bg9nuwDIBeAadJ JaE66doLNkPFHa+78L59b5DSF4ukzXoXhszkI6kLxh/uqlJoXGunEKAti/LSX3vqcwE4 nh5Hg0Mxkwk/iYI4DzjmlVduDXumd/QtwVfKDIsYYn514IxZSSOJylsin0SrL6bbolQ8 MxJQ== X-Gm-Message-State: AOJu0YwRUgnl9in+IxHXEK9rOYK+99kHyJNJNglaeOttSENgZat8VXeX gLl1BhPNazUQ57H468F/CQTt1ppjiwDVYyZynj0Vmd1/lqgsT0rJHoKxgkl9aKE= X-Gm-Gg: ASbGnct/3QxGKVo3o0PSmwW2Pb2UB35IIOg2TV2pyY5CtFNxXRahJwN5TMCRc8wzW35 EkR9DP15PVa8VZX7iZPqeNZIIrdzt0r6T7dp/FMEOOvn4/1rbw+o8PyF4a6tNM51qQV4Uvnn6Q4 9ABqV6KTYRBUB0ObnYdlOzvzxkBU1MdNfonFSFkdQI5PWvPeKmkWnpcHULt9P+28niqy95BjgkN ig4J4ylez1xjANcA2W5kKZD0Yz87DTjT0i9kX6otsBspnMIoDOsCuHgV0CedEQvkcXL46JWLYj6 JT2rvDxxw5s3R/zHvK+ASyZZPLiwS/i1+M17N/pWEL9tr6tHkqopQnJMT0og8dl+q8/E X-Google-Smtp-Source: AGHT+IFGIeAx26qTWKJ1uStUSiorxj3W9zd5zaQp6aa+YiLg97OtO+P3OwFH26GE363t9Ti3IEIN7w== X-Received: by 2002:a05:6a00:2917:b0:725:eb85:f7ef with SMTP id d2e1a72fcca58-73035142694mr6203009b3a.14.1738774199609; Wed, 05 Feb 2025 08:49:59 -0800 (PST) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-72fe6427a8dsm13084968b3a.54.2025.02.05.08.49.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 05 Feb 2025 08:49:59 -0800 (PST) Date: Wed, 5 Feb 2025 08:49:57 -0800 From: Stephen Hemminger To: Pavel Vazharov Cc: users Subject: Re: IPv4 flows per queue on top of RSS for ixgbe and i40e drivers Message-ID: <20250205084957.02e14a3e@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Wed, 5 Feb 2025 18:21:33 +0200 Pavel Vazharov wrote: > Hi there, > > We have a proxy application on top of DPDK where we use a symmetric > RSS key to receive the packets for a given connection in both > directions on a single queue. In addition to that, we've few IPv4 > addresses where we need to receive their traffic on particular queues. > We use the rte flows functionality with RTE_FLOW_ACTION_TYPE_QUEUE to > achieve that and it seemed to work with the DPDK ixgbe driver. > However, today we tried the same application on top of DPDK i40e > driver and this setup doesn't seem to work there. It prints the > following errors: > `i40e_flow_add_del_fdir_filter(): Conflict with existing flow director rules!` > It seems that the i40e driver doesn't allow adding flow rules on top > of the already set RSS. > > Can somebody suggest a way to achieve what we need with i40e: to use a > symmetric RSS key for most of the traffic but to redirect the traffic > for a few specific IPv4 addresses to particular queues? > > Thanks, > Pavel. If you are mixing RSS and rte_flow the results are not well defined. Many drivers treat all active queues (including those used by rte_flow) as candidates for RSS. If you want to mix, the the safe way is: - don't enable RSS in the device config (rx_mode) - define an rte_flow rule with RTE_FLOW_ACTION_TYPE_RSS with a match all - define a rte_flow rule with RTE_FLOW_ACTION_TYPE_QUEUE that matches the IP and set rule priorities so that specific IP rule matches before the match all. You still maybe at risk of hardware quirks and driver incompatibilities which is part of the problem with rte_flow.