linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Mason <mpeg.blue@free.fr>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: ext2 large block size > page size
Date: Fri, 1 Apr 2011 10:49:12 -0400	[thread overview]
Message-ID: <20110401144912.GF21075@thunk.org> (raw)
In-Reply-To: <4D91C806.10601@free.fr>

On Tue, Mar 29, 2011 at 01:52:38PM +0200, Mason wrote:
> Hello everyone,
> 
> As far as I can tell from a quick Google search,
> there was a push in 2007 to add support for large
> blocks in some file-systems, in particular ext2.
> 
> e.g. cf. http://lwn.net/Articles/239090/
> 
> Was this ever accepted into the main line?
> (It seems to have lived within -mm for a while)

Nope, it never was (as you've by now figured out).

> I'm working with a ST Microelectronics set-top box.
> Here are a few performance results for a 2TB USB HDD:
> block size  4k  :  format = 151 s / mount = 242 s
> block size  8k  :  format =  52 s / mount =  71 s
> block size 16k  :  format =  30 s / mount =  36 s
> block size 32k  :  format =  18 s / mount =  19 s
> 
> Using 4kB blocks makes mount too slow on the STB, which
> is why I'd like to use larger blocks. It would be nice
> if the movies recorded on the STB could also be read on
> a Linux PC.

My guess is the mount time slowness is caused an ancient kernel
running on the ST Microelectronics box which is doing mount-time
sanity checks.  You can disable this with the mount option -o nocheck.

A lot of the rationale for larger block sizes was obviated by the use
of more advanced file systems, such as ext4, which have other methods
of dealing with the inefficiencies caused by smaller block sizes.  If
your main complaint with using a 4k block size on the set-top box was
the mount-time slowness, that can be fixed with the nocheck mount
option.

Regards,

							- Ted

  parent reply	other threads:[~2011-04-01 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 11:52 ext2 large block size > page size Mason
2011-04-01 14:13 ` Mason
2011-04-01 14:49 ` Ted Ts'o [this message]
2011-04-01 15:53   ` Mason
2011-04-01 16:29     ` Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110401144912.GF21075@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mpeg.blue@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).