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 BF6D0A0560; Tue, 18 Oct 2022 10:13:05 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 587714021D; Tue, 18 Oct 2022 10:13:05 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 1D1D940143 for ; Tue, 18 Oct 2022 10:13:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666080783; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ctqwXwDa7CtgOGgSQCHbF4IXUzX0VEf4SJKLxBGKcjE=; b=Bue6Nt5KX1IuqbN27PwmlbNva9+3OqaCP3GRcuhm/KVwzGGcQRt+HfHRZQUnqgj6OAaPXs EJzg8MFSHq60tOEvU8kcENQFE7SfKP8QqwryTYrqDPKQpsEt8pQ1lMp0J1uE0WH/kYBxy5 9lAs9EsFjCg7cm0c4PHUw7UGItI9ycU= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-609-pHHf6JRwMzG84twlEP1SVw-1; Tue, 18 Oct 2022 04:13:02 -0400 X-MC-Unique: pHHf6JRwMzG84twlEP1SVw-1 Received: by mail-wm1-f70.google.com with SMTP id q14-20020a7bce8e000000b003c6b7debf22so6534311wmj.0 for ; Tue, 18 Oct 2022 01:13:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:references:to:from:subject:cc:message-id:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=ctqwXwDa7CtgOGgSQCHbF4IXUzX0VEf4SJKLxBGKcjE=; b=pjxqV1TI91SnAa/qwpRSNNaG7CLaKqGa//Y3xFTGNkeJS2fVvp/4W9StI3H75+4YcI i3ufnbFUFYya+l0pcOGKCk80CwJ96eDAW9FULuNdHKdOIEQi8KfnzfGXMtYy/NAIeEP4 fVDMPyd3yna5dCq1t8ORyO+YZ3h0mj4pElyERlxINzP8lMsrRSYuCA9By1uiSRiYBe8F QEcL7J1ERxPWF/0bH34tzZoQ8OXymgYlHdj1uBQLiSP6jn/KXGLGVUh6t8NtA2ZaujKp RUXee6GSB6i2Gs6WJAOFLVjYTBjKXM5xgCxNP2VRWsBH9xHnNChOzgDO31fpIYf8/YQW 7Qbg== X-Gm-Message-State: ACrzQf29DkUYd140w7ecje1LMRQE7yF7NG1CCZeTZOD1BOGQ7PMhVzpJ fyp6O02M5BBtBf+Q5xWINP/RsfpPrYVg2jmLZVThO2DvtV5xl6V88kXvcpXOx2zlPiUKB720Dlh Fj3M= X-Received: by 2002:adf:f501:0:b0:22c:cbea:240a with SMTP id q1-20020adff501000000b0022ccbea240amr1093414wro.78.1666080780869; Tue, 18 Oct 2022 01:13:00 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6HXLpKWyZ13PjHNq241N+RQz2L229u2w3GItnLUFFfdUjkmj7ids5k4S3UAEC4oBaAMXc9UQ== X-Received: by 2002:adf:f501:0:b0:22c:cbea:240a with SMTP id q1-20020adff501000000b0022ccbea240amr1093405wro.78.1666080780650; Tue, 18 Oct 2022 01:13:00 -0700 (PDT) Received: from localhost (2a01cb000f483e0055ae3800781b5cbc.ipv6.abo.wanadoo.fr. [2a01:cb00:f48:3e00:55ae:3800:781b:5cbc]) by smtp.gmail.com with ESMTPSA id t18-20020a5d6a52000000b0022af865810esm10197320wrw.75.2022.10.18.01.12.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Oct 2022 01:13:00 -0700 (PDT) Mime-Version: 1.0 Date: Tue, 18 Oct 2022 10:12:59 +0200 Message-Id: Cc: "Ilya Maximets" , "David Marchand" , "Aaron Conole" , "Eelco Chaudron" , "Kevin Traynor" Subject: Re: rte-flow: unmatched ingress traffic default action From: "Robin Jarry" To: "Ori Kam" , "NBU-Contact-Thomas Monjalon (EXTERNAL)" , "dev@dpdk.org" X-Mailer: aerc/0.12.0-104-g43ae7781d12b References: In-Reply-To: X-Mimecast-Spam-Score: 1 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 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 Hi Ori, Ori Kam, Oct 18, 2022 at 09:41: > > Should I read "general expectation" as a simple recommendation or is > > it a requirement from the RTE flow API? > > I think the wording in the doc should change since it is not clear. So > let me clarify it. > > The idea of isolated mode is that the DPDK application will only get > traffic that the application actively requested. > > When working in isolated mode (relevant only for ingress traffic), the > DPDK port can only receive traffic that the application configured > a matching rule. If no matching rule was set the packet is moved to > the next application/kernel or dropped if no such application/kernel > exists. Oh I was not clear enough. I *don't* use the isolated mode. The "general expectation" I am referring to seems to be in the non-isolated mode. > > Can I expect *all* ingress traffic *not* matching ether_type=3D0x1234 > > to be redirected to queues 0 and 1 following the default RSS > > algorithm? > > No, all traffic not matching the rule will be moved to the kernel in > case of a bifurcated driver, MLX5 for example, or dropped assuming > there is no other application with a matching rule. This is also in regular (non-isolated) mode? Thanks! Robin