From: Chris Wedgwood <cw@f00f.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [RFC] support multiple max offset limits for a single superblock
Date: Fri, 30 Nov 2007 09:14:14 -0800 [thread overview]
Message-ID: <20071130171414.GA5048@puku.stupidest.org> (raw)
In-Reply-To: <47503BB5.2010501@sandeen.net>
On Fri, Nov 30, 2007 at 10:35:01AM -0600, Eric Sandeen wrote:
> I could do the same for ext4, but Chris Mason prodded me to think of something
> more generic... this is what I came up with.
I think it (for now) should remain in the few file-systems that are
affected to avoid making a new ->i_op right now. If it turns out this
is a more commonly need in the future we could do this, but it seems a
bit heavy handy just yet given at present.
Also, it might turn at that it makes sense to to on-the-fly conversion
in the filesystem (where applicable) at some later stage, so this
wouldn't be useful there. I assume it's probably hard to convert a
large bitmap-based ext4 file to an extent-based one (how large can a
transaction be?) but that might not always be the case and it's
probably fine for smaller files.
> (BTW another option would be to convert old-format files when
> accessed, but that has its own set of tradeoffs...)
I think doing that where possible makes more sense. As I said above
I'm not sure how easy that is to do for all files, but then again fsck
could take care of those if prodded.
prev parent reply other threads:[~2007-11-30 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 16:35 [RFC] support multiple max offset limits for a single superblock Eric Sandeen
2007-11-30 17:14 ` Chris Wedgwood [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=20071130171414.GA5048@puku.stupidest.org \
--to=cw@f00f.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.