From: Andreas Dilger <adilger@clusterfs.com>
To: "Jure Pečar" <pegasus@nerv.eu.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ixt3
Date: Tue, 17 Oct 2006 02:51:30 -0600 [thread overview]
Message-ID: <20061017085130.GX6221@schatzie.adilger.int> (raw)
In-Reply-To: <20061017103617.cb1a34c2.pegasus@nerv.eu.org>
On Oct 17, 2006 10:36 +0200, Jure Pečar wrote:
> http://www.cs.wisc.edu/adsl/Publications/iron-sosp05.pdf
>
> I think I got this link from OLS papers or from fs workshop ... and I really like what it says.
>
> How many of ixt3 features are going to be implemented in ext4?
None, yet. The journal checksum code has been brought into a basically
"ready-to-go" state, and there is also work to add checksums to the group
descriptors, so there is some chance that this will be added before ext4
is declared "closed".
Nothing done yet to checksum inodes, superblock, file index
or extent blocks. None of the retry code has been looked at.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-10-17 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 8:36 ixt3 Jure Pečar
2006-10-17 8:51 ` Andreas Dilger [this message]
2006-10-17 9:06 ` ixt3 Jure Pečar
2006-10-17 9:22 ` ixt3 Andreas Dilger
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=20061017085130.GX6221@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=pegasus@nerv.eu.org \
/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