From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [Lsf-pc] [LSF/MM TOPIC] a few storage topics Date: Tue, 24 Jan 2012 14:14:14 -0500 Message-ID: References: <20120119094637.GA23442@quack.suse.cz> <4F1BFF5F.6000502@panasas.com> <20120123161857.GC28526@quack.suse.cz> <20120123175353.GD30782@redhat.com> <20120124151504.GQ4387@shiny> <20120124165631.GA8941@infradead.org> <186EA560-1720-4975-AC2F-8C72C4A777A9@dilger.ca> <20120124184054.GA23227@infradead.org> <20120124190732.GH4387@shiny> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andreas Dilger , Andrea Arcangeli , Jan Kara , "linux-scsi@vger.kernel.org" , Mike Snitzer , Christoph Hellwig , "dm-devel@redhat.com" , fengguang.wu@gmail.com, Boaz Harrosh , "linux-fsdevel@vger.kernel.org" , "lsf-pc@lists.linux-foundation.org" To: Chris Mason Return-path: In-Reply-To: <20120124190732.GH4387@shiny> (Chris Mason's message of "Tue, 24 Jan 2012 14:07:32 -0500") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com List-Id: linux-fsdevel.vger.kernel.org Chris Mason writes: >> All three filesystems use the generic mpages code for reads, so they >> all get the same (bad) I/O patterns. Looks like we need to fix this up >> ASAP. > > Can you easily run btrfs through the same rig? We don't use mpages and > I'm curious. The readahead code was to blame, here. I wonder if we can change the logic there to not break larger I/Os down into smaller sized ones. Fengguang, doing a dd if=file of=/dev/null bs=1M results in 128K I/Os, when 128KB is the read_ahead_kb value. Is there any heuristic you could apply to not break larger I/Os up like this? Does that make sense? Cheers, Jeff