From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 06FD1A04EF; Wed, 3 Jun 2020 10:11:08 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 83F721C1B2; Wed, 3 Jun 2020 10:11:07 +0200 (CEST) Received: from huawei.com (szxga07-in.huawei.com [45.249.212.35]) by dpdk.org (Postfix) with ESMTP id D0B331C1AB for ; Wed, 3 Jun 2020 10:11:05 +0200 (CEST) Received: from DGGEMS409-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id D83CAABDC0B5695D90CF; Wed, 3 Jun 2020 16:11:03 +0800 (CST) Received: from [127.0.0.1] (10.67.103.119) by DGGEMS409-HUB.china.huawei.com (10.3.19.209) with Microsoft SMTP Server id 14.3.487.0; Wed, 3 Jun 2020 16:11:02 +0800 To: Ferruh Yigit , "Burakov, Anatoly" CC: dev , Qi Zhang , Andrew Rybchenko References: From: oulijun Message-ID: <88c50d79-b278-2f7f-7e4f-1dc35f682654@huawei.com> Date: Wed, 3 Jun 2020 16:11:02 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.103.119] X-CFilter-Loop: Reflected Subject: Re: [dpdk-dev] Questions Questions about hash function enum X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 在 2020/6/3 1:13, Ferruh Yigit 写道: > On 6/1/2020 2:31 AM, oulijun wrote: >> Hi Ferruh Yigit and others >> >> I am learning data structure defined by dpdk framework and I noticed >> a data structure definition below: >> >> enum rte_eth_hash_function { >> RTE_ETH_HASH_FUNCTION_DEFAULT = 0, >> RTE_ETH_HASH_FUNCTION_TOEPLITZ, /**< Toeplitz */ >> RTE_ETH_HASH_FUNCTION_SIMPLE_XOR, /**< Simple XOR */ >> /** >> * Symmetric Toeplitz: src, dst will be replaced by >> * xor(src, dst). For the case with src/dst only, >> * src or dst address will xor with zero pair. >> */ >> RTE_ETH_HASH_FUNCTION_SYMMETRIC_TOEPLITZ, >> RTE_ETH_HASH_FUNCTION_MAX, >> }; >> >> I have a little difficulty understanding that for the comment: >> >> /** >> * Symmetric Toeplitz: src, dst will be replaced by >> * xor(src, dst). For the case with src/dst only, >> * src or dst address will xor with zero pair. >> */ >> >> if user configure rss func for symmetric toeplitz, Rss type must be >> updated at the same time? >> >> if user configure rss func for xor, rss type must be empty and the queue >> number is zero? >> >> Must it be restricted like this? If so, what is his benefit? >> >> Looking forward to your reply > > cc'ed Qi & Andrew > > As far as I understand that comment is only describing the Symmetric Toeplitz > behavior. I don't see any rss type or queue number limitation. > Hi Qi & Andrew if user configure rss func for symmetric toeplitz, RSS types must be updated at the same time? flow create 0 ingress pattern end actions rss func symmetric_toepilitz types tcp end / end if use the following cmd: flow create 0 ingress pattern end actions rss func symmetric_toepilitz types end / end it is wrong and the driver will print the error info. How to understand this limitation? Thanks Lijun Ou > > . >