From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id A1052C35274 for ; Thu, 21 Dec 2023 20:42:27 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 1E9B06B00B7; Thu, 21 Dec 2023 15:42:27 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 171D86B00B8; Thu, 21 Dec 2023 15:42:27 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 062826B00B9; Thu, 21 Dec 2023 15:42:27 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id E9C3B6B00B7 for ; Thu, 21 Dec 2023 15:42:26 -0500 (EST) Received: from smtpin05.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id BDB2340D15 for ; Thu, 21 Dec 2023 20:42:26 +0000 (UTC) X-FDA: 81591998292.05.EBF62FA Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf09.hostedemail.com (Postfix) with ESMTP id D98A9140015 for ; Thu, 21 Dec 2023 20:42:24 +0000 (UTC) Authentication-Results: imf09.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=OEWlua4W; spf=none (imf09.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1703191345; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=WHHdz+wtVwYfCmTJUyu+3iOhIuWJtXHqo98nT5qe+5U=; b=YLE5Tw3A6USCzmXk6YipiiiiFvJU3fwc3HDXU4G/bEVue+/xRlsM4zsWXhBeLS0ks5VWiX k2xLQ/n0rtiPl48FLaR8DNMqnSgN/ksP0t1d7it9IHLsC8BdsKz7N/T72scoSg7Cal5AIc 5BnKjSfDIUayVQaU8cdyqBUqOUHWM5Y= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1703191345; a=rsa-sha256; cv=none; b=s+BCmiLPJvQI2w535cDABpiKMzAWhQAaJPhfi+IJZ1Ae2BMQF9Jzw0Yq9QQ2b9ue4fjPmU 8wtRxrXMBvp07JBzOtLZXUcL43Xel7DNG2jdveDdp1hZNdf1gZ+8dv2CNrKi+EgWp2doBc ri2nXfC3j2eFchsfnKBUG0RfWlNX6Cc= ARC-Authentication-Results: i=1; imf09.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=OEWlua4W; spf=none (imf09.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=WHHdz+wtVwYfCmTJUyu+3iOhIuWJtXHqo98nT5qe+5U=; b=OEWlua4W+Rjf6fYb2pKNd8mklz SAMeX5fGAJPMfXuanODlQ3CcAY824bvRhsevJV37jaUbhkHUm3P3Ud4Pi0Cw7dgr5OHdSqo03FenM ib4oHKHAUp3jgcZHfgjODZ/Qy9fqy317ppd5Q2EzAvCNXw2S+U58lb0bQHoumeFf3A0t7NyMsQmad Ji86yLXz7KSUz5J5HUiCu/ckqd6mFT+9cDdURrW4JOagkpKpNtm40uUMsPQukuHv1xOqNp42bkPGS XDBAgpyqR/V9rE9SJo86VXheefrbY5st7V1iGDPIFEIcUWAXDTsc5cW9lw1HjkxP6J3giwphYXjkw 6380Q7VQ==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1rGPrx-0067eC-RW; Thu, 21 Dec 2023 20:42:14 +0000 Date: Thu, 21 Dec 2023 20:42:13 +0000 From: Matthew Wilcox To: Bart Van Assche Cc: Hannes Reinecke , lsf-pc@lists.linuxfoundation.org, linux-mm@kvack.org, linux-block@vger.kernel.org, linux-scsi@vger.kernel.org, "linux-nvme@lists.infradead.org" Subject: Re: [LSF/MM/BPF TOPIC] Large block for I/O Message-ID: References: <7970ad75-ca6a-34b9-43ea-c6f67fe6eae6@iogearbox.net> <4343d07b-b1b2-d43b-c201-a48e89145e5c@iogearbox.net> <03ebbc5f-2ff5-4f3c-8c5b-544413c55257@suse.de> <5c356222-fe9e-41b0-b7fe-218fbcde4573@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5c356222-fe9e-41b0-b7fe-218fbcde4573@acm.org> X-Rspamd-Queue-Id: D98A9140015 X-Rspam-User: X-Rspamd-Server: rspam11 X-Stat-Signature: z16mgp3u5on84ru7rj7w76ks4zyzrxsf X-HE-Tag: 1703191344-115168 X-HE-Meta: U2FsdGVkX19KRdVFycP4T3Tk6inGTZhWtOBaeZwQSIPBXw/c/0UkjQnG6QNThi3voar7LyFPFmSSR6OPb2eW74xYRU30qT2aaKeF/pooOXy7AxTAoReWxIOqwJXWYT3HGSWTvqoJq42x85XK+sZ8vEHS98sPlTPozo0QswBiV9c5ByxGd16qrLZ3Nl2ZMzKBNHMThDzrdpxO9izfa98AZjZNFpzJxAhkD8FgtF/LjRSfx+2aekgjrJx8hw8imcch190dmZ8VRuukWJC/aB7uuzClfXxOWojDlPMbqPqn1jHov1oiOjrPe/0DrHWnsRJhu8mp/WQJxNa8IWwiJkJOdoQvDuKqrvH5PkReNzOQ4z+n4xnfghLJTbeBtqUuCelxGQ1Y1zmepXKIHaFhdaK85F1DH5h4G4RL377GR/PWur0+LvVCCdzM0g0XonalKsJMbMcnm/kEZugJAiOsxOcZ/n3zd7kJ3QGhcq+CC9X2WgHp3c1Ce3kB1rpmfheLlOleVjepC/R+c+czkBr3VXNcUv4jd3PB9uuwhHRqpZE8cO0hRyhZvO0eSXxl5th795oF0w+Hw6ZyGNaeZNfmTN1kO8QrQ3su6zR+RbMEsGJ2K2HBPaVmatJcA7CcT11+bzIySsabno0DJLo3zEFdYtqR/PvDm5PaH1I7zsSrqSBjlA8Tk8P3VIhAUY9tejLqJWyyzy3PVz78fqsBUQjx3DQZkcdhampYi9qkTLOqns9dAduw9EHaxuE+x49YbB+Tf6XxFK60/gOeCLi376ZwNm7vj6dXKinsGDhqKnPey/D5L7CSi0+VQDR5slO0aAJfh50y8qz3hzpCuAJQiacScoIbnG6GH0QWFHkw5zBzd7mPZdx0kI+1xBeol6qJlRV417ql X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Thu, Dec 21, 2023 at 12:33:08PM -0800, Bart Van Assche wrote: > On 12/20/23 07:03, Hannes Reinecke wrote: > > I would like to discuss > > > > Large blocks for I/O > > > > Since the presentation last year there has been quite some developments > > and improvements in some areas, but at the same time a lack of progress > > in other areas. > > In this presentation/discussion I would like to highlight the current > > state of affairs, existing pain points, and future directions of development. > > It might be an idea to co-locate it with the MM folks as we do have > > quite some overlap with page-cache improvements and hugepage handling. > > Hi Hannes, > > I'm interested in this topic. But I'm wondering whether the disadvantages of > large blocks will be covered? Some NAND storage vendors are less than > enthusiast about increasing the logical block size beyond 4 KiB because it > increases the size of many writes to the device and hence increases write > amplification. It's LSF/MM. If this session is being run as a presentation rather than discussion, it's being done wrongly. So if you want to talk about the downsides, show up and talk about them.