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 DED3245648; Thu, 18 Jul 2024 17:36:15 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8BC5142FED; Thu, 18 Jul 2024 17:36:12 +0200 (CEST) Received: from mail-pf1-f177.google.com (mail-pf1-f177.google.com [209.85.210.177]) by mails.dpdk.org (Postfix) with ESMTP id A76A44025E for ; Thu, 18 Jul 2024 17:36:10 +0200 (CEST) Received: by mail-pf1-f177.google.com with SMTP id d2e1a72fcca58-70b04cb28acso718503b3a.0 for ; Thu, 18 Jul 2024 08:36:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1721316970; x=1721921770; 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=g40pcCjdgWCVngk+oNNnWM8Or1Jzlif/k1XpWbBBh74=; b=NYgZfOzdw1fRjDIWvH+keHSesPAfaQ09efFOb8Bmw5o5D3/yZcIxp4/TMnhRTvF7Y7 ltxsVQPEwIXFN9TFF457GVbED9cGAObXlQCgcMAQWCMzDkFMDraR+VsiCVbhWIUq8NpE kLPUxgDJ3MJUGoGq2ms+gX8TNJVeOiEEU7PNM3fSBwhtp3dEBcYRSAHyPxrxE2DEvYcU IHVAZnxD2ghOwzY1DWfdfqTWmhptdLVmtqlFS380Z7qqKX6wfJ1s6TnVtHQlMuYZHfQE EddCGf/BQyxYXDUUshQ0skQ37YLJ046+gNXUdPhn9TZ8FvPzTLnSzEkLPTyGUb14To5t nOjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721316970; x=1721921770; 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=g40pcCjdgWCVngk+oNNnWM8Or1Jzlif/k1XpWbBBh74=; b=o2h3PTeYqCInr5W2NoGbV3xcf1fPMvYAMKjnFxEG9pqaZ/zSxIuKs5GJlqHHuUGp+r p8yuLLRM3yyZUFrWSkExle1sodDlqF5Ht03bZmNQaPn5p9w3GR6RkPRUMw2bz9dG0QqN UNBEgxoGaoal83Q3DQ8TLK/Yk1rBxbmmwiia+U7GhET3rlzXt3xe76bg7yMtotCxLQpa zUZb04brwf7HbseNrHYJgKRtPz/BatQfJc4Ih0Prm8rZ3MCEzezypt/Sw3N3d9Fyc+3V 5G3s8/b8otTRDUn7MC0sCmXlB4o4qNbvJW+V9BHIdtyryVz9R+Wr9VbLTT8uAPZQD16u PuWQ== X-Gm-Message-State: AOJu0YxRWLurIOtTwAhUFVgE/X5EDu9f79nfokIyhm8YJJRtHd+fmbwy wM0FQtU3fcMO0aHszvGt4wbgkNlUXRK7EJkkQ+bbMXPPwBpTarqTnIOrjkJh1MY= X-Google-Smtp-Source: AGHT+IH1AMTpeS/+cyMW/tSVOFGBCU2ga17Ld3oqEgtsed1aGxDcD5VhI6mWye6LSwz6BTy5kPkYsg== X-Received: by 2002:a05:6a00:1ace:b0:706:5c4c:1390 with SMTP id d2e1a72fcca58-70ceeb4b4bbmr4822957b3a.7.1721316969639; Thu, 18 Jul 2024 08:36:09 -0700 (PDT) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-70b7eb9e290sm10220147b3a.5.2024.07.18.08.36.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Jul 2024 08:36:09 -0700 (PDT) Date: Thu, 18 Jul 2024 08:36:07 -0700 From: Stephen Hemminger To: Raghavan V Cc: "dev@dpdk.org" , "users@dpdk.org" Subject: Re: FDIR packet distribution with specific multiple RX queues. Message-ID: <20240718083607.2b70d734@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 Thu, 18 Jul 2024 11:36:43 +0000 Raghavan V wrote: > Is there any way to distribute packets evenly (Like RSS) to specific multiple RX queues in RTE_FLOW_ACTION_TYPE_QUEUE DPDK Flow director? > > Desired action: > > uint16_t queue_indices[] = {10, 11, 12, 13, 14, 15}; > struct rte_flow_action_queue queue = {.index = queue_indices}; > struct rte_flow_action action[]={ > [0]={.type = RTE_FLOW_ACTION_TYPE_QUEUE,.conf = &queue}, > [1]={.type = RTE_FLOW_ACTION_TYPE_END} > }; You want RTE_FLOW_ACTION_TYPE_RSS uint16_t queue_indices[] = {10, 11, 12, 13, 14, 15}; struct rte_flow_action_rss rss = { .types = RTE_ETH_RSS_UDP | RTE_ETH_RSS_TCP, .queue_num = RTE_DIM(queue_indicies), .queue = queue_indicies, }; struct rte_flow_action action[]={ [0]={.type = RTE_FLOW_ACTION_TYPE_RSS,.conf = &rss}, [1]={.type = RTE_FLOW_ACTION_TYPE_END} }; > Is this action limited to drivers specific? Yes, drivers implement only what hardware can support.