From: tytso@mit.edu
To: Sunil Mushran <sunil.mushran@oracle.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-ext4@vger.kernel.org, Joel Becker <Joel.Becker@oracle.com>,
Mark Fasheh <mfasheh@suse.com>
Subject: Re: e4defrag and immutable files
Date: Tue, 1 Jun 2010 18:26:43 -0400 [thread overview]
Message-ID: <20100601222643.GI4426@thunk.org> (raw)
In-Reply-To: <4C057B68.9040205@oracle.com>
On Tue, Jun 01, 2010 at 02:28:08PM -0700, Sunil Mushran wrote:
>
> We had thought of the term static because we wanted the inode to
> be frozen. Entire metadata including the mapping. Our aim is to
> do away with cluster locks for such inodes. For ios, we were planning
> to limit it to only odirect and not change the mtime. That also means
> no links, touch. Yes, "static" does not fit it like a glove but that's the
> best we could come up with.
Hmm, maybe "fixed_metadata"? The one thing that worries a bit is not
touching mtime is definitely icky. I suppose it would improve
performance even on local-disk file systems if we don't update mtime,
ctime, or atime. So maybe that would be useful for folks who are
trying to extract the last bit of performance out of their enterprise
database.
One thing I do like about fixed_metadata is that as far as chattr and
lsattr is concerned 's' and 'S' are already taken. But 'f' and 'F'
aren't allocated yet. :-)
- Ted
next prev parent reply other threads:[~2010-06-01 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 20:14 e4defrag and immutable files H. Peter Anvin
2010-05-28 21:21 ` Greg Freemyer
2010-05-28 22:06 ` H. Peter Anvin
2010-06-01 19:12 ` Eric Sandeen
2010-06-01 19:32 ` Sunil Mushran
2010-06-01 19:49 ` tytso
2010-06-01 20:14 ` Greg Freemyer
2010-06-01 21:00 ` Eric Sandeen
2010-06-01 21:28 ` Sunil Mushran
2010-06-01 22:26 ` tytso [this message]
2010-06-01 22:51 ` Sunil Mushran
2010-06-02 7:28 ` H. Peter Anvin
2010-06-02 18:02 ` Sunil Mushran
2010-06-08 22:12 ` H. Peter Anvin
2010-06-09 1:10 ` Joel Becker
2010-06-09 1:44 ` tytso
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=20100601222643.GI4426@thunk.org \
--to=tytso@mit.edu \
--cc=Joel.Becker@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=sandeen@redhat.com \
--cc=sunil.mushran@oracle.com \
/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).