Received: by 10.192.165.148 with SMTP id m20csp1688889imm; Thu, 26 Apr 2018 00:20:18 -0700 (PDT) X-Google-Smtp-Source: AIpwx49v+f3hGtTilWWF4EKOHOFhLXIARRxNafoDmRkdKvl97qTAARs57XMlDaKWilOFsOBdb8Ly X-Received: by 10.98.81.197 with SMTP id f188mr30947704pfb.136.1524727218735; Thu, 26 Apr 2018 00:20:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524727218; cv=none; d=google.com; s=arc-20160816; b=ERl7v1Yp/hmZOSH6VeYmPZJTdnhQCeiiFAFxJEaLq51zHFolKv7Ui9nFifA2CzEwp8 V3InAVJv6UpFIWb666Hz5sJWQk+CkR5w8ZSVRxFxSzEC4Guh7PSyRwYuSBqBs3Bjab7h zeI1KemYvNPN2INGfYx831mg38TQCEm1QHayUlZY6ZCLK+050XZgWTb9ckDElvFtz7wF T0yFMzjjyC1sHl1wxiQ7rNuySHC2EiIeTMW/hU1c+vY0sjbtrSmQuu7fxC36qfZ1pemc xNtH4IycImzUSfuR5ApSF90Ueb+dr81TmVsPb1uTuKyv4NzUfSQxqy/qeSfGxNpUT/nn Jd8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=WjglUAJW8b1lyjQ8+Kph5yWiRDuPjZpflohMjYYvr8I=; b=gDJCvFsjK6y5a/pN4XToDBvlWsROq1kVSwcYoAV1wJ0tcz7ga8Sf0q7fZHpoWqNi6u 72mS9HlI2ST7b8vFpjen/6ugtXZMaX8e1F/dNiilKAu4w9p1HIxuUDZs8TeNvkYAl3Hf Hgp8KpHJZI/3q3X0ig7c5QEIjYgnxPpnP6sDR9R78v1Xqd1rS/R8Wz4Yg3Zy98RDZZyA jVFhal/oSQph9SpbBkT7rs088BX9v7N4b7dppJX+l0YXopqC2RfJBRM4WDBCprkNfhVE gIXrjVerU0wIU7m5r6ljE092g2ic+pd722SS/yy2AB/EOTMp6Y1UDiBth9FiW/HQXTJG 9/8w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v6-v6si18680696plo.534.2018.04.26.00.20.04; Thu, 26 Apr 2018 00:20:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754070AbeDZHSx (ORCPT + 99 others); Thu, 26 Apr 2018 03:18:53 -0400 Received: from verein.lst.de ([213.95.11.211]:40714 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752148AbeDZHSv (ORCPT ); Thu, 26 Apr 2018 03:18:51 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id AAD597090F; Thu, 26 Apr 2018 09:20:33 +0200 (CEST) Date: Thu, 26 Apr 2018 09:20:33 +0200 From: Christoph Hellwig To: Jens Axboe Cc: Christoph Hellwig , iommu@lists.linux-foundation.org, linux-arch@vger.kernel.org, linux-block@vger.kernel.org, linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org, netdev@vger.kernel.org, "David S. Miller" , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/5] ide: kill ide_toggle_bounce Message-ID: <20180426072033.GA14700@lst.de> References: <20180424181625.22410-1-hch@lst.de> <20180424181625.22410-3-hch@lst.de> <5aaca0d3-417f-57f3-969f-b4c777c3fd48@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5aaca0d3-417f-57f3-969f-b4c777c3fd48@kernel.dk> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 24, 2018 at 08:02:56PM -0600, Jens Axboe wrote: > On 4/24/18 12:16 PM, Christoph Hellwig wrote: > > ide_toggle_bounce did select various strange block bounce limits, including > > not bouncing at all as soon as an iommu is present in the system. Given > > that the dma_map routines now handle any required bounce buffering except > > for ISA DMA, and the ide code already must handle either ISA DMA or highmem > > at least for iommu equipped systems we can get rid of the block layer > > bounce limit setting entirely. > > Pretty sure I was the one to add this code, when highmem page IO was > enabled about two decades ago... > > Outside of DMA, the issue was that the PIO code could not handle > highmem. That's not the case anymore, so this should be fine. Yes, that is the rationale. Any chance to you could look over the other patches as well? Except for the networking one for which I'd really like to see a review from Dave all the users of the interface are block related.