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 X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 67EE2C43381 for ; Fri, 15 Feb 2019 17:20:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3487521925 for ; Fri, 15 Feb 2019 17:20:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="HuEpBYFa" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727377AbfBORUN (ORCPT ); Fri, 15 Feb 2019 12:20:13 -0500 Received: from mail-pf1-f196.google.com ([209.85.210.196]:38556 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726139AbfBORUN (ORCPT ); Fri, 15 Feb 2019 12:20:13 -0500 Received: by mail-pf1-f196.google.com with SMTP id q1so5127143pfi.5 for ; Fri, 15 Feb 2019 09:20:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=H7HVTISxhVEDjSBgu4kG0IZzy912/GlO6i+kUuwuZR4=; b=HuEpBYFamg46dI1AzIs3DBLdDM2/tOeaGMVajpOj77aJihMuGHQww9ZZGWJkLs0VjI MoXka9nyfr/MVO6biw/U/oaoZIPBc35Zv/IKM5GQKX1uT+rNZfjkmjp5i/gYJQOHWtBk gWETl8Bij2wV4PQ5Ztn0wiBPOtP+mm7c1nKW6qfQKe5BR5B2h0YtNa1WO9Yqxs9CNgXU H3MOWu4muKjsjb9rXD/a+m0a6KBum3D3Q/BOOr8vj7xMwWcX3tGuL5fBbdbnPoEj16IW 5GgOFmqNaUi9qafgPYtrytgkVZaMguZ6ePKdYovDA1aFF+dgg0FK4qIxBF/24zp0FBjp sxtQ== 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:user-agent; bh=H7HVTISxhVEDjSBgu4kG0IZzy912/GlO6i+kUuwuZR4=; b=DoPpKErISydr1+isgELbB/ErOkx9O39IUPZpdr2NW9L4xd4zp05kESDnzViQOvIUYs IAh35wJJfVIUY/FTNw+CZRr5pA9y4P4FGjhNhXVu4svEnbR8bNd/bOMwD+me52tEEPaA jrzdclDcEAm2ttYVKzVvLOYXNE83lB9PxtKcGuc6d33KIe4jeuT69D9c7LV3LEdhxbIe LTUGEG3IrDkLS7rfrnIvALnI48s/udr2J/EX4D6kcbMjPDThfxsuKrf04IJt2zsQBzA+ NlKvVeFn91MaORt6kQHRmY1s09TAw1Ntzz07sUMK8N2pc1Hfnvqd5VNexD5vnksfZyHO 1YOA== X-Gm-Message-State: AHQUAubcPk3t6KsKJwwBEHB52rz8WOqo5ujOGlEofhWqReP3ed4gIqTv UuF7VV2UAfpCUoqpN5vK5vidpw== X-Google-Smtp-Source: AHgI3Ia4EmU5DoIynjfm9G3jiUxsgJGLMPBDaXeslS15kDpgmmMomglhTGPByRbVWgwiIMv1eTnnMg== X-Received: by 2002:a63:b447:: with SMTP id n7mr10235448pgu.401.1550251212421; Fri, 15 Feb 2019 09:20:12 -0800 (PST) Received: from ziepe.ca (S010614cc2056d97f.ed.shawcable.net. [174.3.196.123]) by smtp.gmail.com with ESMTPSA id e19sm7055403pfn.145.2019.02.15.09.20.11 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 15 Feb 2019 09:20:11 -0800 (PST) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1guh9n-0000Go-28; Fri, 15 Feb 2019 10:20:11 -0700 Date: Fri, 15 Feb 2019 10:20:11 -0700 From: Jason Gunthorpe To: Shiraz Saleem Cc: dledford@redhat.com, davem@davemloft.net, linux-rdma@vger.kernel.org, netdev@vger.kernel.org, mustafa.ismail@intel.com, jeffrey.t.kirsher@intel.com Subject: Re: [RFC v1 00/19] Add unified Intel Ethernet RDMA driver (irdma) Message-ID: <20190215172011.GB30706@ziepe.ca> References: <20190215171107.6464-1-shiraz.saleem@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190215171107.6464-1-shiraz.saleem@intel.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Fri, Feb 15, 2019 at 11:10:47AM -0600, Shiraz Saleem wrote: > The unified driver is currently being tested on X722 with rdma-core-v22. > X722 is supported by this driver, but only if CONFIG_INFINIBAND_I40IW > is disabled in the kernel. We desire to deprecate or phase out i40iw > from the kernel and can submit patches to do the same. We would like to > move forward with this unified driver model for current and future HW. You need to do better than this.. rdma-core should setup to detect which of the kernel drivers is present and do the right thing. This may require some new infrastructure work, but siw and rxe need this capability as well. > This series was built against rdma-next. > commit 21a428a019c9 ("RDMA: Handle PD allocations by IB/core") > It includes both net and rdma patches for the purposes > of review. It will be split into two separate patch series, one for > net-next and rdma-next once RFC is accepted. > > [1] https://patchwork.kernel.org/patch/10419583/ Be aware we cannot take net-next into rdma. You would be best to submit a clean -rcX based PR to both net and RDMA for your net portion. Jason