From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C3173A53 for ; Mon, 2 Oct 2023 06:04:35 +0000 (UTC) Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 755B39B; Sun, 1 Oct 2023 23:04:30 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 0C27A68D1C; Mon, 2 Oct 2023 08:04:25 +0200 (CEST) Date: Mon, 2 Oct 2023 08:04:24 +0200 From: Christoph Hellwig To: Jerry Snitselaar Cc: Greg Kroah-Hartman , Hannes Reinecke , Chris Leech , Christoph Hellwig , Rasesh Mody , Ariel Elior , Sudarsana Kalluru , Manish Chopra , Nilesh Javali , Manish Rangankar , John Meneghini , Lee Duncan , Mike Christie , Hannes Reinecke , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/3] cnic,bnx2,bnx2x: use UIO_MEM_DMA_COHERENT Message-ID: <20231002060424.GA781@lst.de> References: <20230929170023.1020032-1-cleech@redhat.com> <20230929170023.1020032-4-cleech@redhat.com> <2023093055-gotten-astronomy-a98b@gregkh> <2023093002-unlighted-ragged-c6e1@gregkh> <2023100114-flatware-mourner-3fed@gregkh> <7pq4ptas5wpcxd3v4p7iwvgoj7vrpta6aqfppqmuoccpk4mg5t@fwxm3apjkez3> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7pq4ptas5wpcxd3v4p7iwvgoj7vrpta6aqfppqmuoccpk4mg5t@fwxm3apjkez3> User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net On Sun, Oct 01, 2023 at 07:22:36AM -0700, Jerry Snitselaar wrote: > Changes last year to the dma-mapping api to no longer allow __GFP_COMP, > in particular these two (from the e529d3507a93 dma-mapping pull for > 6.2): That's complete BS. The driver was broken since day 1 and always ignored the DMA API requirement to never try to grab the page from the dma coherent allocation because you generally speaking can't. It just happened to accidentally work the trivial dma coherent allocator that is used on x86.