Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp466943ybl; Tue, 7 Jan 2020 09:12:22 -0800 (PST) X-Google-Smtp-Source: APXvYqzVhiiya9XMLXWCC3uifKh6rnEHRPwkv7G3P7m/lqrarbMD0fKVExq3b7DfuLB7bx2Hzlqg X-Received: by 2002:a05:6830:1292:: with SMTP id z18mr824597otp.148.1578417142383; Tue, 07 Jan 2020 09:12:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578417142; cv=none; d=google.com; s=arc-20160816; b=obudjXenZ0Xa/upE6KNerop/nAEY6rnsgWg3AU9DfyWfOi+tL5DCBjRvLLCaH5tbl7 xMU/zhmjzj1fZQ20Y2e5MjXf86OSUVB890UwynkosFNBtPZHdthoBWgzuDmChs5sk4cG cE+aAcG/hoev+lB+wyvPn0iLtElclMk0Jv7YWfEfjHsu2tfP6hzcu5YuO5uLbHb1hYyP 8W/o7que8sc40m10Uk2MsY5lbAhO8cU06OnVANL6sbztpQ3wjCYTv0t2389TYtHguj30 +cjwLIqttvmIE/oUwd0zaXGHJ5Rkhv8LN31cOdNcVAJUhg6WokG+gH6MK+I1AVGsoW6A g7/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=MykBpHGqDmNw1Kq3+rI7RYkeRroSPARdHI4+IRGnYBY=; b=dHAYZQAc70h8hpndogxlH1M3PtOnCGfF1tIzt7+Jcch1p5/t2P1WO3i1uUe2DHHDZa btSTw8Xy/wW7Avm+JQ11DDP9Bhb2KakSvO8SwJth1EBrZ9gJS/VvIqNiC2OUs330K0Bq Zm2YhrunZBds4r5E29Wd+eLlx7rfn7viWw5DYalzRdLzSnCKL0u7hdMXNDx3Q/3NpVx3 VtrIU7Y0hxvHdPqnegp4/v8MQeosWsX7BiwiHS52wrC3KVqf45RmMpeGmtEUzAxoGWnF lnKn7KIsuMIZJyL2hvoimALCcwpviBDkIS+y3Vh4uhpcCXqit8lBvXY3LaupRH2CWzag ihrg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-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 t2si167434otq.196.2020.01.07.09.12.06; Tue, 07 Jan 2020 09:12:22 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-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-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728391AbgAGRL2 (ORCPT + 99 others); Tue, 7 Jan 2020 12:11:28 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:54267 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728503AbgAGRL1 (ORCPT ); Tue, 7 Jan 2020 12:11:27 -0500 Received: from callcc.thunk.org (guestnat-104-133-0-111.corp.google.com [104.133.0.111] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 007HBAi5008204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 Jan 2020 12:11:11 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id EFF6E4207DF; Tue, 7 Jan 2020 12:11:09 -0500 (EST) Date: Tue, 7 Jan 2020 12:11:09 -0500 From: "Theodore Y. Ts'o" To: Jan Kara Cc: Ritesh Harjani , Xiaoguang Wang , Ext4 Developers List , joseph.qi@linux.alibaba.com, Liu Bo Subject: Re: Discussion: is it time to remove dioread_nolock? Message-ID: <20200107171109.GB3619@mit.edu> References: <20191226153118.GA17237@mit.edu> <9042a8f4-985a-fc83-c059-241c9440200c@linux.alibaba.com> <20200106122457.A10F7AE053@d06av26.portsmouth.uk.ibm.com> <20200107004338.GB125832@mit.edu> <20200107082212.GA25547@quack2.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200107082212.GA25547@quack2.suse.cz> Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org Hmm..... There's actually an even more radical option we could use, given that Ritesh has made dioread_nolock work on block sizes < page size. We could make dioread_nolock the default, until we can revamp ext4_writepages() to write the data blocks first.... - Ted