Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4167697imw; Tue, 19 Jul 2022 00:44:37 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vGI/ezCfRs5SuxIk5pp5dp7s3UsMT37sEPMl7OYkku5MG3D1+V7tVmi2T8WB8JhWfQc8A4 X-Received: by 2002:a63:594f:0:b0:412:96c7:26f7 with SMTP id j15-20020a63594f000000b0041296c726f7mr29431453pgm.110.1658216677166; Tue, 19 Jul 2022 00:44:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658216677; cv=none; d=google.com; s=arc-20160816; b=Ye5xm1QZeKQdxycNza1XDt4eTx0pjjU4i08ikgrNJ8cm5ejmgvrERz/8QjHCnLZ5+9 Tf5xr/mswHTqgOrCTS2lsrMihFGU7DGxDwtsNj0eIqAxvyA58dlTkCJ2tImVL9SS5Pz0 ZIZzr4J5dskZJ0dY4ljM+QAQmRgOQKMMbA961VdjNUktssSUIQA9Zap+J/vMUH93slt7 gmTCzypSHpPhbnhscDcR43G9DxjoiaEBbn0LpKtujoa/w0x6i1SA3JOzQh9sYDmdfvNu D9BHll0dW7s7Scm9IczoURTRofb5CrW1fid9V9TrwZr+85z4e1ghN/YJCh2Dj8VJ0DFh qU9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=sdIM2hy7/uqs0GUfns6XhD4NdvSpYxz/E1zY03Ds0CI=; b=wGsvSc2QODXOqTMF6+vUbEsB9efvqDeMs+PVBIUbSMDPOvIXe5YqlnpY+TedpEkoB4 POLOXJAG7Ynp97n9odwFprF+Vknxr2Vff8GAWjAnu1u5RCWs81Vus9ccS/LPqAD/QIbw /EH9rN1DYQlh54uyhOb2kWruKBLz3DKEGePiltk3o9nUBR6GnBWpmEDapUkuKjwqn8Eb k10RQfOS2wePwZoN1FsZHg5j1AwqbtfNh/zT8vNymZLrnt8FQ+zqtnA7RZWD7CPSf6T/ ylJ3+SBAeNYiGBjWAKuiX4ELGRGzXTtl6+Hdq0l1QQ3RuyJbtfSyBo/Vy0cq9gHvpW9h EXJg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f4-20020a637544000000b00412ac5a482csi18609746pgn.854.2022.07.19.00.44.21; Tue, 19 Jul 2022 00:44:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233829AbiGSHKh (ORCPT + 99 others); Tue, 19 Jul 2022 03:10:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43270 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234338AbiGSHKe (ORCPT ); Tue, 19 Jul 2022 03:10:34 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 368B22BD2; Tue, 19 Jul 2022 00:10:33 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id D975368AA6; Tue, 19 Jul 2022 09:10:28 +0200 (CEST) Date: Tue, 19 Jul 2022 09:10:28 +0200 From: Christoph Hellwig To: John Garry Cc: Damien Le Moal , joro@8bytes.org, will@kernel.org, jejb@linux.ibm.com, martin.petersen@oracle.com, hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org, iommu@lists.linux.dev, linux-scsi@vger.kernel.org, linuxarm@huawei.com Subject: Re: [PATCH v6 4/6] scsi: sd: Allow max_sectors be capped at DMA optimal size limit Message-ID: <20220719071028.GA28633@lst.de> References: <1657797329-98541-1-git-send-email-john.garry@huawei.com> <1657797329-98541-5-git-send-email-john.garry@huawei.com> <6725df4f-4e27-3320-8b7b-22ba15a07866@opensource.wdc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 19, 2022 at 08:05:30AM +0100, John Garry wrote: > Christoph has now applied this (thanks, BTW), so would you like me to > follow up with a patch on top with a comment? Please do.