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 1F3E6A04B0; Sun, 18 Oct 2020 15:33:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C23C7BAFA; Sun, 18 Oct 2020 15:32:59 +0200 (CEST) Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) by dpdk.org (Postfix) with ESMTP id 81C21BAE0 for ; Sun, 18 Oct 2020 15:32:57 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.nyi.internal (Postfix) with ESMTP id D8B6B5801CB; Sun, 18 Oct 2020 09:32:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sun, 18 Oct 2020 09:32:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= PVnEpEv1KgwbSDvaNwkKjcKqdQ5Q+v8tA3ANNmKevmA=; b=LwjGh73rLGUMwSxB x+d19BxzUBJVgpj2i33/KePRr4OltCImgfEzcgofzSlxPb6Xi5xm4j5cLPBqQed5 kDPdZtFCleqajsTVwMXE6pkRapXZVmSuqvE5ABd5XjdWFjXfUyjAwFPIvhbcJQDo QUNNQFG3ETLleodRKx8rW2nrgWQFlzXaILQs42lp/xRU1YDxcK5XVoIEUQPL+uJb KvWJq8cpTNPl0pN7KKbpICDubSacrpOkaw6HkjHLA8NkKf76dVODtY05zjwIYE8H lgtOMIzJHMbbikMCkYwq0XSkv2EMD7Ax5zTfEu+MssrKh/wOlRhGLj0HOgAZOX+V VtDjlw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=PVnEpEv1KgwbSDvaNwkKjcKqdQ5Q+v8tA3ANNmKev mA=; b=XzlasyQWTRre1yO6+df9wPLcCIDyqhwI1MLf7Lqn+fhZHV+PSga20wcfm KUEy/6nlWKYGrg2syW+p0GmnwItYFAkgI/sdQAxn7E9hW9OiJ9yhme4NOVSxPkLH Lnd0ExQVeymNdTjVFH5SkTizVq8mfAyLJChiBVxigKnUO4tV8/y30MV/PNe9thuL avsJbPXJHc6lXSrU9p2dPEHZRFl06OURFWLoYXtR/xGt7LPHNrti/ELMsbKsugXQ kcjCcMfX3Uhut/+F/h9kkQ1aq16tOhoHu+UWzXN8OMSk/docCdgdmTkJLO8/h7ns bTrWkBqT9oVWz+r/LjUk0x1f2Gf1A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrieelgdeiiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 25CBE3064680; Sun, 18 Oct 2020 09:32:54 -0400 (EDT) From: Thomas Monjalon To: Guy Kaneti Cc: "orika@mellanox.com" , "dev@dpdk.org" , Jerin Jacob Kollanukkaran , Smadar Fuks , Dovrat Zifroni , "bruce.richardson@intel.com" , "konstantin.ananyev@intel.com" , "david.marchand@redhat.com" , "ferruh.yigit@intel.com" , "honnappa.nagarahalli@arm.com" , "ktraynor@redhat.com" Date: Sun, 18 Oct 2020 15:32:47 +0200 Message-ID: <4674736.E9P3XzJaBd@thomas> In-Reply-To: References: <20200908123144.26444-1-guyk@marvell.com> <3312477.OZWf0QDG0M@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [EXT] Re: [PATCH 1/2] examples/l3fwd-regex: add regex based l3fwd 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" 18/10/2020 13:53, Guy Kaneti: > From: Thomas Monjalon > > > From: Guy Kaneti > > > > > > Add regex based l3fwd application > > > inline with normal l3fwd. only LPM is supported. > > > > The trend is to reduce the number of example applications. > > Do you think regex could be an option in the original l3fwd? > > The regex operation is not a direct networking functionality and is not a type of forwarding. > The purpose of the application was to show an example of regex operation with networking. > I think it should stand by itself. If it was only regex, yes it would make sense as standalone. But mixing with networking forwarding could be in the same app.