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 CEBCDA0093; Tue, 4 Jan 2022 17:54:47 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5981840042; Tue, 4 Jan 2022 17:54:47 +0100 (CET) Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com [209.85.216.51]) by mails.dpdk.org (Postfix) with ESMTP id E994A40040 for ; Tue, 4 Jan 2022 17:54:45 +0100 (CET) Received: by mail-pj1-f51.google.com with SMTP id c9-20020a17090a1d0900b001b2b54bd6c5so16175pjd.1 for ; Tue, 04 Jan 2022 08:54:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=kaKzA2B/r7wmYHe1b0g6p+SJj4c3+zpwm0tVFYBo1/0=; b=XsOp+JFqDLNdWFd0+HGL9khVfddyDlLGLIMDJk1iI5npjejUg1z+f/bvWGtWpZRwbL /LkoArS+QsLeQEZTaPQrz1+J0+FWVTWbp1zZAEzb4m5sDbIYV2pEYnHZ9xiT29YtJBFL zJWumb9ygy+xPd1UHrSH7cn2mmFKYpLxtC9DOPkc969eMAO2VGCOQNlADLwSkHpbwU7W nt1ClF8AFcvMVFKJlOD7ecHUgfkLyhpvQZuEbjUBA86IMXPUj23g/9hdmA1k/y56yCP3 JHEh0WnGVz/5asKRqZHHpEOkIvbzaZYTSUWnPZQxLNopqLriuuLKKVpkD38mDGZK/9YK B1QQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=kaKzA2B/r7wmYHe1b0g6p+SJj4c3+zpwm0tVFYBo1/0=; b=BUI7npxpI1Lo+bLdLnStHTUwhYOIdn3QPw05feTgAZOqYm8i1K9jHpm3TNorkTlQjl dmsnhw9PvWhhHoXqlrZ1kv7B+O7niaGxy6gWlUmV2VsJ/g3JHL74Dsr9I1igu6FUw5VR 73UwNw9TwdewmoqyAEc5/ivMmgilqgNfdhSP7xk/UQ7nC6qoYF//FlyZPQq6d2S2gCPh b795+DNAMAmpeu+juH31PLfr040XkjY+vtaDTF2nNwDgs0N/STjRskZdPqwMHv6kG6JW 8q3s8hAcGML7uBDL4YRpkBFPm1PjP9gf6zM6fygv6Mp+X18yh0LQsN5wI36rhd6sa5tC y4uA== X-Gm-Message-State: AOAM5333p4BjNgYUF557LUwnyVFgulmm/cui3yO2nyEYvq4Q3tegE8ar xL7OV1bK4LCXqE/wXfVAoMjvsQ== X-Google-Smtp-Source: ABdhPJwu/BUDj5vdXo69LifK1ncJNqBPsX8ViH8YzdO1SapcBTJMjDkEaLFoRyj6RqovL/+8o1rw4w== X-Received: by 2002:a17:90a:fd95:: with SMTP id cx21mr62024653pjb.54.1641315285059; Tue, 04 Jan 2022 08:54:45 -0800 (PST) Received: from hermes.local (204-195-112-199.wavecable.com. [204.195.112.199]) by smtp.gmail.com with ESMTPSA id x6sm35985177pge.50.2022.01.04.08.54.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Jan 2022 08:54:44 -0800 (PST) Date: Tue, 4 Jan 2022 08:54:42 -0800 From: Stephen Hemminger To: Thomas Monjalon Cc: Ivan Malov , Adrien Mazarguil , dev@dpdk.org, Andrew Rybchenko , orika@nvidia.com Subject: Re: Understanding Flow API action RSS Message-ID: <20220104085442.4e406f2a@hermes.local> In-Reply-To: <4677833.GXAFRqVoOG@thomas> References: <76f98055-c517-5185-b79-d16ec5ef5ff@oktetlabs.ru> <4677833.GXAFRqVoOG@thomas> 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 Tue, 04 Jan 2022 13:41:55 +0100 Thomas Monjalon wrote: > +Cc Ori Kam, rte_flow maintainer > > 29/12/2021 15:34, Ivan Malov: > > Hi all, > > > > In 'rte_flow.h', there is 'struct rte_flow_action_rss'. In it, 'queue' is > > to provide "Queue indices to use". But it is unclear whether the order of > > elements is meaningful or not. Does that matter? Can queue indices repeat? The order probably doesn't matter, it is like the RSS indirection table. rx queue = RSS_indirection_table[ RSS_hash_value % RSS_indirection_table_size ] So you could play with multiple queues matching same hash value, but that would be uncommon. > > An ethdev may have "global" RSS setting with an indirection table of some > > fixed size (say, 512). In what comes to flow rules, does that size matter? Global RSS is only used if the incoming packet does not match any rte_flow action. If there is a a RTE_FLOW_ACTION_TYPE_QUEUE or RTE_FLOW_ACTION_TYPE_RSS these take precedence. > > When the user selects 'RTE_ETH_HASH_FUNCTION_DEFAULT' in action RSS, does > > that allow the PMD to configure an arbitrary, non-Toeplitz hash algorithm? No the default is always Toeplitz. This goes back to the original definition of RSS which is in Microsoft NDIS and uses Toeplitz. DPDK should have more examples of using rte_flow, I have some samples but they aren't that useful.