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 B06F2A0487 for ; Thu, 4 Jul 2019 11:52:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6F9E51B9B3; Thu, 4 Jul 2019 11:52:06 +0200 (CEST) Received: from mail-wm1-f65.google.com (mail-wm1-f65.google.com [209.85.128.65]) by dpdk.org (Postfix) with ESMTP id 721BD1B9A7 for ; Thu, 4 Jul 2019 11:52:05 +0200 (CEST) Received: by mail-wm1-f65.google.com with SMTP id x15so5092570wmj.3 for ; Thu, 04 Jul 2019 02:52:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=b5C02seOx+uyZ/FJLE9knnuXXRA0DWrfNz+BD/e+Ojo=; b=UJLO2Bc3KeLMIDDXiRMuyyI7aaWOndQSbF9w/vEIj3MsuYUzuLopcRPVUTA4lIHTge YPBtCiuzEUEGN+mLP9zrrXRAJ5AVGz9PggJDtdNqSmvF1A0GPl2RoUsIJiISOCWd21fb 4Vou+IUtJRVQZV/4vojfWiesNE3wQvjkUMjfhwa3tdqxnM2s33XSY1IbKojKS8o+1QBF 5Z2HySYPN1dHwXB91GzFtHqY2/0wlXyGut9muAEJ7KOqJqr73wuuOpqg1sOi0Gxry2wV ymwT3achre5diKiEm37gecaLqAgt4o//LJ33A/aJKAKHsCx5sFxpEykmHcRWelPC1ZZP 6S0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=b5C02seOx+uyZ/FJLE9knnuXXRA0DWrfNz+BD/e+Ojo=; b=WhO5XGfHpe4MKI3kmBPczgnJkvcGl8Idly3BllxJc0YUm6LW/GybwfY+l//bYqj+FO Z1Cr1OdWfRacRW774cVgoNRRSAD6Wce7SuGomk+88U6T/QV6x9Hro2cFL8HcaWF3mp1j KXS9f83842ItCgT8kKskoTRLrP8R8zSFO4844i4SK/GaOl4U/1A+49otzYLvDhWZPrnY 6iPAogoqKqac3T6WSGSiCbT53aVgmNrte0bcQVAmDWe3Q6EprKyyyC1+94U4JMGwp3Oz vd5RZZzFYeMbOkkw82k5hgABXXL0Y2BsfGfBSODZiOqMkfueo4J+EHcdhyL7R9y1Cxs0 8AuQ== X-Gm-Message-State: APjAAAWmy9sFQz0CKhT24FHLaO1/d6gp3fPNkGQMnobTdTw2paRtx+v8 ZADYmh3IUY7gcdwdztfYNoYDwQ== X-Google-Smtp-Source: APXvYqwIjpIbDa4GHiOIUdTFqYSWDYurK3eHjnaOFO68QqBNwMENnqgBDGI8vLbSBkrtHaFjlEDqTA== X-Received: by 2002:a1c:c747:: with SMTP id x68mr11975095wmf.138.1562233925150; Thu, 04 Jul 2019 02:52:05 -0700 (PDT) Received: from 6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id o7sm1158787wmc.36.2019.07.04.02.52.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jul 2019 02:52:04 -0700 (PDT) Date: Thu, 4 Jul 2019 11:52:02 +0200 From: Adrien Mazarguil To: Jack Min Cc: Ori Kam , Wenzhuo Lu , Jingjing Wu , Bernard Iremonger , John McNamara , Marko Kovacevic , "dev@dpdk.org" Message-ID: <20190704095202.GL4512@6wind.com> References: <20190624154018.128379-1-jackmin@mellanox.com> <5d9e2fcd3a1bf439b0cff354ca5b5bf1f43e090d.1562058723.git.jackmin@mellanox.com> <20190703152516.GI4512@6wind.com> <20190704055231.bpwbvbd6g2zosbl6@mellanox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190704055231.bpwbvbd6g2zosbl6@mellanox.com> Subject: Re: [dpdk-dev] [PATCH v4 4/4] app/testpmd: match GRE's key and present bits 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" On Thu, Jul 04, 2019 at 05:52:43AM +0000, Jack Min wrote: > On Wed, 19-07-03, 17:25, Adrien Mazarguil wrote: > > On Tue, Jul 02, 2019 at 05:45:55PM +0800, Xiaoyu Min wrote: > > > support matching on GRE key and present bits (C,K,S) > > > > > > example testpmd command could be: > > > testpmd>flow create 0 ingress group 1 pattern eth / ipv4 / > > > gre crksv is 0x2000 crksv mask 0xb000 / > > > gre_key key is 0x12345678 / end > > > actions rss queues 1 0 end / mark id 196 / end > > > > > > Which will match GRE packet with k present bit set and key value is > > > 0x12345678. > > > > > > Signed-off-by: Xiaoyu Min > > > > I'm wondering... Is matching the K bit mandatory if one explicitly matches > > gre_key already or is this a specific hardware limitation in your case? > > > > If there is gre_key item MLX5 PMD will force set HW matching on K bit, > From HW perspective it is mandatory. But, from testpmd (user) > perspective, I agree with you, user needn't set matching on K bit if > they already explicitly set gre_key item. OK, makes sense. > > Perhaps we could document that the K bit is implicitly matched as "1" in the > > default mask when a gre_key pattern item is present. If a user explicitly > > Yes, I should document this. > So it should be documented in __testpmd_funcs.rst__ ? No it would be a change in the GRE_KEY item itself at the rte_flow API level (rte_flow.h) & documentation (rte_flow.rst). The flow rules created by testpmd must be an exact translation of user input, as a debugging tool it can't request something that wasn't explicitly written. > > spec/mask K as "0" and still provides gre_key, the PMD can safely ignore the > > gre_key item. > > > > Well, actullay, when a user explicitly set spec/mask K as "0" and still > provide gre_key item, MLX5 PMD will implicitly set match on K bit as > "1", just ingore the K bit set by user. Not good then. You should spit an error out if it's an impossible combination. You can't match both K == 0 *and* a GRE key, unless perhaps if key mask is also 0, e.g.: gre crksv is 0x0000 crksv mask 0xb000 / gre_key value spec 0x00000000 value mask 0x00000000 This is merely an overly complex way for telling the PMD that one wants to match packets without GRE keys that you could technically support. > The reason is wanna keep code simple, needn't to get > information from other item (gre) inside gre_key item, or vice verse. PMDs typically maintain context as they process the pattern. The GRE pattern item is guaranteed to come before GRE_KEY, so you already know at this point whether users want to match K at all, and if so, what value they want it to have. > And, I think, when a user provides a gre_key item, most probably, they do > really wanna match on gre_key. What do you think? Depends. They may want to match all GRE traffic with a key, doesn't matter which, in order to process it through a different path. To do so they could either: 1. Use the GRE item only to match K bit == 1. 2. Use the GRE_KEY item to match a nonspecific key value (mask == 0). 3. Use a combination of both. I think you can easily support all three of them with mlx5 if you support partial masks on GRE keys (I haven't checked), even if you're unable to specifically match the K bit itself. [...] > > > @@ -755,6 +759,13 @@ static const enum index item_mpls[] = { > > > > > > static const enum index item_gre[] = { > > > ITEM_GRE_PROTO, > > > + ITEM_GRE_CRKSV, > > > > CRKSV may be unnecessary in this patch if the K bit is documented and > > implemented as described in my previous comment. > > > > Well, actully, we also wanna testpmd can match on C,S bits with K bit > together so we can test on gre packet with key only or csum + key, or > csum + key + sequence. OK no problem. Perhaps you could make this easier by allowing users to match individual bits, let me explain: The flow command in testpmd is a direct interface to manipulate rte_flow's structures. The "crksv" field doesn't exist in rte_flow_item_gre, its name is "c_rsvd0_ver". Testpmd must use the same in its command and internal code. However since bit-masks are usually a pain to mentally work out, you can provide extras for convenience. The "types" field of the RSS action (ACTION_RSS_TYPES) is an extreme example of this approach. So I suggest adding ITEM_GRE_C_RSVD0_VER taking a 16-bit value like CRKSV, and complete it with ITEM_GRE_C_BIT, ITEM_GRE_S_BIT and ITEM_GRE_K_BIT addressing the individual bits you would like to expose for convenience. [...] > > You should have named this field "value" then, i.e.: > > > > - ``value {unsigned}``: key value. > > > > OK, I'll update it. Please remember to update it in rte_flow.h and documentation as well, thanks. -- Adrien Mazarguil 6WIND