Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1979390imu; Tue, 6 Nov 2018 07:17:39 -0800 (PST) X-Google-Smtp-Source: AJdET5daGKHqhQ8wzxDscKp8BqPFcnTNqj+s8HGceJqGvjNujq4/NS6Z2W/jE7KsD1QmsNivHjhi X-Received: by 2002:a63:9c1a:: with SMTP id f26mr24205342pge.381.1541517459212; Tue, 06 Nov 2018 07:17:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541517459; cv=none; d=google.com; s=arc-20160816; b=KI+QCVKDJBZOPFQQEkedrqgW++tRod5+Gz8pcFCYpClly8RBPgyu2Y4yA+dOv184aP mRNtm4E2U1jVuCDo/wXeymFsbM6Pbj8eEKKWTEuBWciV3BRgaqOIcQrozgNFUjg0egC3 WTUaFjQD9AOsDb0Iz97yY1Ly0jKcBDK9Se4H2ghU4W5NVUjqqc4ZCmuI4D/qFpddsmPf mE9AZztU8FhVTvGhAjDWc4KGcIMlhWvQYV+8ztMZI8KRodhrjau1DCxHwGff+l+vX1DD nPwhGIfFD84lqnln483m5GvtJhcvYbqOF2nCiAmVeVE/4ECCnbANPdGQt9Ta89Eexxur IFzA== 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=4L45PsqUCsccooyabUC16T0tA/q+ySD4y/mIiBHBVX0=; b=s9m9vCEvCLA/GDyKDqK8WLLFlpjElK20WqEhZMh+KDQN4p2TGTdNQCneAb9xZL9VYG LF4P2AJ2n4SwYyc8sS8mesB44lfRXMtcYu+EpNwbPgR0YOhrfGBQQJJJQ4gBQxLCBoj8 KbMozDMsp73aVzgU7IF7UkZaOo+Umsmez0abjQSX/qu7X3eZynk8nmh4Oqv8Qrnke2ff 1eavRYsJd1xQIyghxhB5sfIeB3URGCgrPmYjj0M8JK54LomGBqqGxV0niwNcwRmhvDRE hHnHYopgV9S0hU4h5KWhXwvDMKa9RVPG1r90jyKIZRJlbCOMF9ZIxsc82gDV6+avG9TX IVpQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1-v6si12176902plt.225.2018.11.06.07.17.23; Tue, 06 Nov 2018 07:17:39 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387884AbeKGAlv (ORCPT + 99 others); Tue, 6 Nov 2018 19:41:51 -0500 Received: from mga01.intel.com ([192.55.52.88]:34270 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729574AbeKGAlu (ORCPT ); Tue, 6 Nov 2018 19:41:50 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Nov 2018 07:16:09 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,472,1534834800"; d="scan'208";a="84388452" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by fmsmga008.fm.intel.com with ESMTP; 06 Nov 2018 07:16:09 -0800 Date: Tue, 6 Nov 2018 08:14:02 -0700 From: Keith Busch To: Ming Lei Cc: Johannes Thumshirn , Ming Lei , Jens Axboe , linux-block , Hannes Reinecke , Linux Kernel Mailing List , Jan Kara , Sagi Grimberg Subject: Re: [PATCH] block: respect virtual boundary mask in bvecs Message-ID: <20181106151402.GA6020@localhost.localdomain> References: <20181105102301.9752-1-jthumshirn@suse.de> <20181105105548.GC12367@ming.t460p> <7c649b43-f952-cf94-93d6-44fb153acced@suse.de> <20181105120153.GD12367@ming.t460p> <3c3dd9c2-4240-7bb5-c0ff-af6f2e479c31@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 06, 2018 at 10:56:52PM +0800, Ming Lei wrote: > > This patch makes sense on >4KB PAGE_SIZE. Granted existing blk_queue_virt_boundary() users all appear to be at least 4k, the block API doesn't enforce that. Some unlikely device may require an even smaller alignment in the future, which would benefit from this patch. But yes, the changelog description is a bit confusing to me if the sighting came from a 4K arch.