From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E2BC0ECAAD5 for ; Tue, 30 Aug 2022 18:56:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229712AbiH3S4h (ORCPT ); Tue, 30 Aug 2022 14:56:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45352 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229565AbiH3S4f (ORCPT ); Tue, 30 Aug 2022 14:56:35 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 73F3677541 for ; Tue, 30 Aug 2022 11:56:34 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 14A61B81D8A for ; Tue, 30 Aug 2022 18:56:33 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 46181C433D6; Tue, 30 Aug 2022 18:56:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661885791; bh=4848dtnEVL059zSIhDoR07cyDQkAoEjFn0GhbT7XNEA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=GsPLKiWVVwbuVIk9O7wAoy2x/uj/DcGlED2LXTKXvX0GIvtNsN4q0DgAXz7IP9H18 +6giKkNyWPqd1KrNs8/JNyyQNLAcDTZ9PA57Ch2XLx8d4AA7FfXSIIdm2vHP4jx/ba fg1A7Qj4rPAjj5qFPHl+plUfPf774jeeIO7s16mlrJJrPudNpjMOYGZs7d8YY/zYK7 UtUQFgywjks2bJUDv0DUbDk0qS37rItzZNeYnVQm1jOSfCVtE+wQcJQI6BI1IQVJ79 fK80hmGp2p+oQG6D57xxgKZlmMHSZcdvXlanWrmHRU8vXfv7Lox4iOvQrpxBT+DNNl lW/bXW6QLFcyw== Date: Tue, 30 Aug 2022 11:56:27 -0700 From: Jakub Kicinski To: Jason Gunthorpe Cc: Leon Romanovsky , Steffen Klassert , "David S. Miller" , Eric Dumazet , Herbert Xu , netdev@vger.kernel.org, Paolo Abeni , Raed Salem , Saeed Mahameed Subject: Re: [PATCH xfrm-next v3 0/6] Extend XFRM core to allow full offload configuration Message-ID: <20220830115627.27099213@kernel.org> In-Reply-To: References: <20220825143610.4f13f730@kernel.org> <20220826164522.33bfe68c@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, 30 Aug 2022 14:36:52 -0300 Jason Gunthorpe wrote: > I was meaning rather generically handling the packets in the > hypervisor side without involving the CPU. > > We have customers deploying many different models for this in their > hypervisor, including a significant deployment using a model like the > above. > > It achieves a kind of connectivity to a VM with 0 hypervisor CPU > involvement with the vlan push/pop done in HW. I don't see how that necessitates the full IPsec offload. Sorry, perhaps I assumed we were on the same page too hastily. I was referring to a model where the TC rules redirect to a IPsec tunnel which is then routed to the uplink. All offloaded. Like we do today for VxLAN encap/decap. That necessitates full offload, and therefore can be used as a strong argument for having a full offload in netdev. > We other use-models, like the offloaded OVS switching model you are > alluding to, that is Leon has as a followup.