Received: by 10.192.165.148 with SMTP id m20csp2259898imm; Thu, 26 Apr 2018 08:13:04 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+QYdfEFxcmhhyUiHPWDg2slH6+Nk2llUvw18ty7lsIIa/5wGAQB2y4juUmnFKV/uPtfRCy X-Received: by 10.98.108.69 with SMTP id h66mr32879958pfc.43.1524755584912; Thu, 26 Apr 2018 08:13:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524755584; cv=none; d=google.com; s=arc-20160816; b=SFiTG4xbRmCDHiXc0vwrTCrmtHvSy7h5kWA9YefdhtLy6BwHXJg+d9ApmY6gBYwNWY NoGLKXjeQWt4AdHJw8BFqxOG1niJ97Ka8aSrXbjoIkAJzFS9lEZoNrH1LYujgX9GirwF XwUkmscosd1BoA+RyIxDjK586tvibVRLkfGQZ5IG8BJSHT6E48G9IW6qK8ReTxbekdUD bg1yRZN7ZoJAJPv7ApErMD84EPbAgDl+eBN36B8GgSK0MBhcnKb/kk2+cnKMfpj2/ict len0tQ/KiKvWLxULFOTz3pmxM5ulGnR3l1zpE8tLPejU1moiWOVaVHfltkYy+3bTLY42 slwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=rIjnFhafnS6x7equQG3Um7kF5UpgcZSpxChVNoL4q8E=; b=qrgJrYFGIiK3TiTlLu4zVBMwhanizWQGZhEHyGO5FQBS0mvj+noGqLGJ7HE8nqtxIA NUMd1emg9XTAHxct0Q2aBcoJx9c9eZHNF9q5YMscyj9bBdpqnRBjUFGolOMF2Q6ocnQt 6cvCxlK9GU9iwQE0Y8lE6qrg8fP0fl9bBamm6X2GyjtlbOYHrcdphQNSDGaLo2dY2FP/ 6xMXUiN6CONE+C89C+BtP+HgfqFC9vw4drZfZuxq7paelIchila792nCLBQJ/upY6Xt+ RTTlS21sA8BU9Mg1FAEo6Lb3lD6ESWocdF+EJFB9w/q1O6zwpgvtx42NcxIrHtd2AdSA sGQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=Wh+Ur4wA; 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 r77si18206701pfa.359.2018.04.26.08.12.50; Thu, 26 Apr 2018 08:13:04 -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; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=Wh+Ur4wA; 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 S1756658AbeDZPLj (ORCPT + 99 others); Thu, 26 Apr 2018 11:11:39 -0400 Received: from mail-pf0-f171.google.com ([209.85.192.171]:44615 "EHLO mail-pf0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756481AbeDZPLa (ORCPT ); Thu, 26 Apr 2018 11:11:30 -0400 Received: by mail-pf0-f171.google.com with SMTP id q22so3683199pff.11 for ; Thu, 26 Apr 2018 08:11:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=rIjnFhafnS6x7equQG3Um7kF5UpgcZSpxChVNoL4q8E=; b=Wh+Ur4wAZqM3eZKwRKe/OWkv/st1i5ru69PuxYYLLgnSwI8F9s2XsSKibMcUEIvSRQ 46WdlUA/IPO+AoG0n9mogq30qvB/3cdzDUYwooAIsEz3T1gLAlgEixQZTM2RAEFdFUic 49YWPyNGG46tnD9sYVq8PAorZkfl+rsxM822Mzg2OCZAkP64Xls9g6bD7UmEx3pmWcT1 tW7Bl0HazuEmog+KbtbX3N1BFhBL/B+QBwjHsbcRqNeDHpTRP4ShdFlTqImzCbW+JL37 y3Qwx57QhuW2Wsj4r5chP2LTz9iiCg3KxHMOjey0whRzXkLsMXM9yH+1fqjPh5Hhg2wQ D4Dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=rIjnFhafnS6x7equQG3Um7kF5UpgcZSpxChVNoL4q8E=; b=tR/oMRqPRgyZHE6OIawyVMQEjTtp5Y+kTjGQ+GGiYfeNKVY0FehHL3FcOax/YkGcSf APeg8n7xzVa/olgLJo2lAOqqo6PwwKF7mhNMTHbl7X/sAPpDbqgtoHEvYSLplD3MBEh2 QDCPyAjxHE8TUkXjT+D6H6PglG3NJqvHdJt5eegZnpAt8SIED6+F2yF+Fiy3qpCn2PU/ pi1K8fqs2WzAyEONzCqeZMVDnt5726JNXJpNINMuMHT8IiGxD8F1vhYN7K9lgbVGBiTL uMlcX9GcUbIVb8/rVaPhBYyneAm95MprBF7U7TXTkUT745BKnwubTxZCvplVX1heXfiM FfTw== X-Gm-Message-State: ALQs6tBdh2xGftB09ognTa+zWc8d8/DjeDHE0uszqt7Nkd0KOklv5cdf lAzxePNcB+pdykOCZVGRsOeK9jGBSEM= X-Received: by 10.101.73.7 with SMTP id p7mr28000357pgs.139.1524755489315; Thu, 26 Apr 2018 08:11:29 -0700 (PDT) Received: from [192.168.1.211] (107.191.0.158.static.utbb.net. [107.191.0.158]) by smtp.gmail.com with ESMTPSA id h9sm4378995pgs.29.2018.04.26.08.11.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 08:11:28 -0700 (PDT) Subject: Re: [PATCH 2/5] ide: kill ide_toggle_bounce To: Christoph Hellwig Cc: 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 References: <20180424181625.22410-1-hch@lst.de> <20180424181625.22410-3-hch@lst.de> <5aaca0d3-417f-57f3-969f-b4c777c3fd48@kernel.dk> <20180426072033.GA14700@lst.de> From: Jens Axboe Message-ID: <682db9af-33bc-639d-8930-7a66c30bc644@kernel.dk> Date: Thu, 26 Apr 2018 09:11:21 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180426072033.GA14700@lst.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/26/18 1:20 AM, Christoph Hellwig wrote: > 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. You can add my reviewed-by to 1-3, and 5. Looks good to me. -- Jens Axboe