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 5EE65C636D3 for ; Thu, 9 Feb 2023 01:17:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230044AbjBIBRC (ORCPT ); Wed, 8 Feb 2023 20:17:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52522 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231364AbjBIBQx (ORCPT ); Wed, 8 Feb 2023 20:16:53 -0500 Received: from sin.source.kernel.org (sin.source.kernel.org [145.40.73.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0A0A4DBF9; Wed, 8 Feb 2023 17:16:51 -0800 (PST) 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 sin.source.kernel.org (Postfix) with ESMTPS id 0AEF2CE2357; Thu, 9 Feb 2023 01:16:50 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 92316C433D2; Thu, 9 Feb 2023 01:16:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1675905408; bh=QgD+Wr8/tOUVJeWZJi5X3zVWBTmcoSCWT5R322PQDIc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=k2ZeQq/+6l/C2FsX27s5pBk5+PV99Gf8L+OUXwBsKM6rEhgUP3NLrid7JtVmZyObz 9ifHYnzWsf7xmNUOTwpz6uC8hkHjy8ldh6sLKD7qWGZ6W9q4NhEsACLvmEUTzeci8Q 2oBczZVeIH5UjlhaHvthKT7PbObtIE52lgDyHZsh8pOwiGbFkJiNOuE0EonnqkHHUt 85+hyhdqAoWSJcF+edZJ+ZjhGUKvSbvtEtk1OlXEfkG5HxekMhuLMccp5iCm+rIa3Q YvWedRv9fV+4jL2iNo/tV+MccL4MHB9FkV682SSmGv2mJpozNtC6LZbfCaZxaxLE6A xQaotJB0tuh/w== Date: Wed, 8 Feb 2023 17:16:46 -0800 From: Jakub Kicinski To: Jason Gunthorpe Cc: Saeed Mahameed , Leon Romanovsky , "David S. Miller" , Paolo Abeni , Eric Dumazet , Saeed Mahameed , linux-rdma@vger.kernel.org, netdev@vger.kernel.org Subject: Re: pull-request: mlx5-next 2023-01-24 V2 Message-ID: <20230208171646.052e62fd@kernel.org> In-Reply-To: References: <20230203174531.5e3d9446@kernel.org> <20230206163841.0c653ced@kernel.org> <20230207140330.0bbb92c3@kernel.org> <20230208151922.3d2d790d@kernel.org> <20230208164807.291d232f@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 Wed, 8 Feb 2023 20:59:59 -0400 Jason Gunthorpe wrote: > > Who said IP configuration. > > Please explain to me your vision how we could do IPSEC in rdma and > continue to use an IP address owned by netdev while netdev is also > running IPSEC on the same IP address for netdev traffic. I'm no expert on IPsec but AFAIK it doesn't treat the entire endpoint as a single unit. > I can't see how it is even technically possible. > > Tell me how the NIC knows, on a packet by packet basis, if the IPSEC > or IKE packet should be delivered to netdev or to RDMA. Just a forwarding problem. Whether NIC matches on UDP port or ESP+SPI programmed via some random API is a detail. Could you please go back to answering the question of how we deliver on the compromise that was established to merge the full xfrm offload? There's only so much time I can spend circling the subject.