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 43CDC4619F for ; Wed, 5 Feb 2025 17:53:44 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3713E40270; Wed, 5 Feb 2025 17:53:44 +0100 (CET) Received: from mail-qv1-f44.google.com (mail-qv1-f44.google.com [209.85.219.44]) by mails.dpdk.org (Postfix) with ESMTP id 7566640261 for ; Wed, 5 Feb 2025 17:53:43 +0100 (CET) Received: by mail-qv1-f44.google.com with SMTP id 6a1803df08f44-6dd0d09215aso52514286d6.2 for ; Wed, 05 Feb 2025 08:53:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738774423; x=1739379223; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=b/N8hdJM/2k2HO0539lUONpIZceniHpd4PMyjgB22So=; b=WrPwPQwq+hrJTALT5biTawqVt2mhScq70E/BGvwK3ZXcgjeL77auNLINqrCzosZbXW fafYYDMaSWD63FytK8PIZhXNYDJ8ZD9Jlw8wkXQlF5k4A5aXrrFA8UkZ2P1w4AJo8e5Q oIR7epT5I2iJgUy/z7qUigZvD5prJJdpzocfDa4hXLjs+E+3EXJvEvE9MKzNBd+UPmM+ Z7u5aJii/pTRQeMXlCzM+yWR6r9U6pJOj+XHHfQk8l4kSe9fEHYsWI0Zni5yPDXu/uih NPF2k4z0rZim/NNB6gMvtz/etsEhByipN0Fq93XH+9MjMb6eGxRgIaD+p6HxhhorV4qU FmPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738774423; x=1739379223; h=content-transfer-encoding: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=b/N8hdJM/2k2HO0539lUONpIZceniHpd4PMyjgB22So=; b=RgmsKFhtBL/7MkAyr6yNhV7iAsuP+Ga9I/2/Fmt2CAv0Ul153Vycr6ehbqJzq/sGJ+ gk5Fthna71++cCc2GJPg9oG0iPf1VUw9AV5A76khBPYunc9X5sQA5/+LQy8JKe2B8e5c 0IkjOno1eNsH/MtBKJ5rz7cMLPVOncJKcDr3bwb4iDWgHS9kbjoGmLRwl0JuKUTHl/JT HM0BHoEnurhhRuI94ZpMDNH5oazVELqwkQyuIZz+a1gDkSPE2KktvrDjuR1mRs2nAmby OwKKGB/lDaKfKFotinsRBZAD64Ssb/oS+7OFrgD7ViJecpFXE1LbAMSlZUfTqGDZtSZo 1ktQ== X-Gm-Message-State: AOJu0YyzbSTwGGQce3qLWE+MSKM/+6SBS4MuZi+LFtjHcKKK++XMr674 BfaC30Y8Civ7m9p6CBx3NY+U8hOpTT6ajiDvsjDgMC7TgIrCaT6F0SJ6GeAeVJkJnU+h8Vf21hZ QDD1Bwl50IhjsPuctxnj+RmY3+PGNOA== X-Gm-Gg: ASbGncuGLQbGv1faC88XtgEw1OMkC9DoGCX9t+Ai8xd9dBWE+KxTNMYF4+qgfhstGJM P7sFIpuqvT1DdQMfCIx98PY4wW8/SsYH9Yyjq9UPuPc0iaJuYrhQIhUoaw3kYoNagGwEd+A== X-Google-Smtp-Source: AGHT+IHbGv5pDZDC7SItxrWvfr6QICndt1Mf0/dQmZ3qRDHD+32TLIIEhJD3EphFMxKNQt+6x5uQX4rKnQjSe3jRWN0= X-Received: by 2002:a05:6214:5d06:b0:6d8:a967:8387 with SMTP id 6a1803df08f44-6e42fb0535cmr46384806d6.1.1738774422702; Wed, 05 Feb 2025 08:53:42 -0800 (PST) MIME-Version: 1.0 References: <20250205084957.02e14a3e@hermes.local> In-Reply-To: <20250205084957.02e14a3e@hermes.local> From: Pavel Vazharov Date: Wed, 5 Feb 2025 18:53:32 +0200 X-Gm-Features: AWEUYZluhXK53AgmLTzBdiE5KqGZSyW2JPlK7lyA2rShUW9gI_QoGw-ckkgDdxE Message-ID: Subject: Re: IPv4 flows per queue on top of RSS for ixgbe and i40e drivers To: Stephen Hemminger Cc: users Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, Feb 5, 2025 at 6:50=E2=80=AFPM Stephen Hemminger wrote: > > 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. Thank you for this idea. I'll give it a try. > You still maybe at risk of hardware quirks and driver incompatibilities > which is part of the problem with rte_flow.