Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753788AbaAWM4L (ORCPT ); Thu, 23 Jan 2014 07:56:11 -0500 Received: from imap.thunk.org ([74.207.234.97]:51029 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753690AbaAWM4G (ORCPT ); Thu, 23 Jan 2014 07:56:06 -0500 Date: Thu, 23 Jan 2014 07:55:50 -0500 From: "Theodore Ts'o" To: Dave Chinner Cc: Andrew Morton , "linux-scsi@vger.kernel.org" , "linux-mm@kvack.org" , Chris Mason , "linux-kernel@vger.kernel.org" , James Bottomley , "linux-ide@vger.kernel.org" , "mgorman@suse.de" , "linux-fsdevel@vger.kernel.org" , "lsf-pc@lists.linux-foundation.org" , Ric Wheeler Subject: Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going beyond 4096 bytes Message-ID: <20140123125550.GB6853@thunk.org> Mail-Followup-To: Theodore Ts'o , Dave Chinner , Andrew Morton , "linux-scsi@vger.kernel.org" , "linux-mm@kvack.org" , Chris Mason , "linux-kernel@vger.kernel.org" , James Bottomley , "linux-ide@vger.kernel.org" , "mgorman@suse.de" , "linux-fsdevel@vger.kernel.org" , "lsf-pc@lists.linux-foundation.org" , Ric Wheeler References: <1390410233.1198.7.camel@ret.masoncoding.com> <1390411300.2372.33.camel@dabdike.int.hansenpartnership.com> <1390413819.1198.20.camel@ret.masoncoding.com> <1390414439.2372.53.camel@dabdike.int.hansenpartnership.com> <52E00B28.3060609@redhat.com> <1390415703.2372.62.camel@dabdike.int.hansenpartnership.com> <52E0106B.5010604@redhat.com> <1390419019.2372.89.camel@dabdike.int.hansenpartnership.com> <20140122115002.bb5d01dee836b567a7aad157@linux-foundation.org> <20140123083558.GQ13997@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140123083558.GQ13997@dastard> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 23, 2014 at 07:35:58PM +1100, Dave Chinner wrote: > > > > I expect it would be relatively simple to get large blocksizes working > > on powerpc with 64k PAGE_SIZE. So before diving in and doing huge > > amounts of work, perhaps someone can do a proof-of-concept on powerpc > > (or ia64) with 64k blocksize. > > Reality check: 64k block sizes on 64k page Linux machines has been > used in production on XFS for at least 10 years. It's exactly the > same case as 4k block size on 4k page size - one page, one buffer > head, one filesystem block. This is true for ext4 as well. Block size == page size support is pretty easy; the hard part is when block size > page size, due to assumptions in the VM layer that requires that FS system needs to do a lot of extra work to fudge around. So the real problem comes with trying to support 64k block sizes on a 4k page architecture, and can we do it in a way where every single file system doesn't have to do their own specific hacks to work around assumptions made in the VM layer. Some of the problems include handling the case where you get someone dirties a single block in a sparse page, and the FS needs to manually fault in the other 56k pages around that single page. Or the VM not understanding that page eviction needs to be done in chunks of 64k so we don't have part of the block evicted but not all of it, etc. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/