From: Christoph Hellwig <hch@infradead.org>
To: "Ted Ts'o" <tytso@mit.edu>, Risanecek <risanecek@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: ext2 large block size support - the shocking truth...
Date: Thu, 22 Mar 2012 13:01:27 -0400 [thread overview]
Message-ID: <20120322170127.GA11819@infradead.org> (raw)
In-Reply-To: <20120321212152.GA32041@thunk.org>
On Wed, Mar 21, 2012 at 05:21:52PM -0400, Ted Ts'o wrote:
> It's not an enhanced ext2 as much as it is enhancements primarily in
> the mm layer to allow file systems to use a "larger page" which is
> larger than the native page size of the CPU's MMU. This is the first
> that I've heard of a DVR, or any product in general, actually trying
> to use Christoph Lameter's patches in a shipping Linux system.
>
> If you just need to read and write files from this file system from a
> userspace CLI shell utility, you could just use the programs from the
> e2tools package; they should work just fine. It works much like the
> mtools package do to be able to copy, rename, list directories, of an
> MSDOS file system, but for ext2/3/4 file systems.
>
> Alternatively, you could try to forward port Christoph's patches to a
> modern kernel, or commission someone to port it to a modern for you...
Or the device might have a CPU with larger pages. I've seen various
appliances with ppc CPUs that use 64k page and for special applications
even 256k pages. I've also seen XFS and extN filesystem taking
"advantage" of that (not sure if really helped them with their
workloads, or if they did it just because they could)
prev parent reply other threads:[~2012-03-22 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 20:38 ext2 large block size support - the shocking truth Risanecek
2012-03-21 21:21 ` Ted Ts'o
2012-03-22 17:01 ` Christoph Hellwig [this message]
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=20120322170127.GA11819@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=risanecek@gmail.com \
--cc=tytso@mit.edu \
/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