Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3198149imu; Mon, 28 Jan 2019 00:05:52 -0800 (PST) X-Google-Smtp-Source: ALg8bN5R0/9nowNaLVCHgQfg5Qj8fdbm7iRmS4NpPQLewUVDad5uP6rrS+CY9wSOoUJQ6xZaM//g X-Received: by 2002:a62:76cc:: with SMTP id r195mr20854263pfc.38.1548662752451; Mon, 28 Jan 2019 00:05:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548662752; cv=none; d=google.com; s=arc-20160816; b=gkJQPE6/4nOCjbh7OO8Uki1TLPrVPOh+jwB5Lq9vAGChcpblUVzJ3C7u6ClQZNobEV MsF1aAQFdP69Y5bRLO2eCjkukGAGpQTHzXaGSe6Hl0JyebpXu1NU1++YF8Q2XiJwrDpm HQ3ccG2D1imojp5FpMAkXS+V0hejVz4EhiImKs54u9rqkODElom22v74ukVx5+lKVAqv kZJBaXjpzf+LTRqpBXn+fMb3wGPoBNEcKRoRLicef2AX6UDL5n4XOd+Wour17t6azfm7 iiAc8mFuRPmSuNV+F0Lj6PhlqCWajQbkpb6eAZ/wgkKYOqBURX37pD5MqMBOoBVwsLQi jNEg== 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; bh=mo1y1fTgrIHbeVGoPDwC7ZobcNoLM4tb/FtUERzAywo=; b=oEXj1Rt+o8ttjdWAj7CbJdULZgQVaIh42HNevb2a0Qrxy8aeDqtusW1Fq0wfxRMfv3 87no9YdJ+I6Ueeqb+riVPJEeP84rrNhlheA3X3EyIyuL3JofS6gui293xqUEGFGCjxwn BgiQR6S9GTkZwH44yFESHFJb7vZgXi//RBBEKIaMemNdg01Vl5sze4j3r3BlF9VOLU8K JsuTzRmMwHWeLsJ4Z2GVx71ZawbWgqxYbj7gPtH62ZfCNMsGTeAiszxYkAJQf5vb21EI 7m6SvNJGJn0bSprSopBrsNBpM8DXOOvq1PCafqjbdSwCw6LhOQDzHjbG75WAb8USkuqe KYTg== 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 b8si31440987pgi.575.2019.01.28.00.05.37; Mon, 28 Jan 2019 00:05:52 -0800 (PST) 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 S1726774AbfA1IF3 (ORCPT + 99 others); Mon, 28 Jan 2019 03:05:29 -0500 Received: from verein.lst.de ([213.95.11.211]:38394 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726638AbfA1IF2 (ORCPT ); Mon, 28 Jan 2019 03:05:28 -0500 Received: by newverein.lst.de (Postfix, from userid 2407) id 8CFC668DCF; Mon, 28 Jan 2019 09:05:26 +0100 (CET) Date: Mon, 28 Jan 2019 09:05:26 +0100 From: Christoph Hellwig To: Joerg Roedel Cc: Christoph Hellwig , "Michael S . Tsirkin" , Jason Wang , Konrad Rzeszutek Wilk , Jens Axboe , virtualization@lists.linux-foundation.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, jfehlig@suse.com, jon.grimm@amd.com, brijesh.singh@amd.com, jroedel@suse.de Subject: Re: [PATCH 5/5] virtio-blk: Consider virtio_max_dma_size() for maximum segment size Message-ID: <20190128080526.GA3874@lst.de> References: <20190123163049.24863-1-joro@8bytes.org> <20190123163049.24863-6-joro@8bytes.org> <20190123213139.GD9032@lst.de> <20190124084011.GJ32526@8bytes.org> <20190124084221.GB19441@lst.de> <20190124095150.GL32526@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190124095150.GL32526@8bytes.org> 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 Thu, Jan 24, 2019 at 10:51:51AM +0100, Joerg Roedel wrote: > On Thu, Jan 24, 2019 at 09:42:21AM +0100, Christoph Hellwig wrote: > > Yes. But more importantly it would fix the limit for all other block > > drivers that set large segment sizes when running over swiotlb. > > True, so it would be something like the diff below? I havn't worked on > the block layer, so I don't know if that needs additional checks for > ->dev or anything. Looks sensible. Maybe for now we'll just do the virtio-blk case that triggered it, and we'll do something like this patch for the next merge window. We'll also need to apply the same magic to the DMA boundary.