From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Felipe Monteiro de Carvalho <felipemonteiro.carvalho@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: Which features should I implement in my ext4 reader?
Date: Mon, 19 Aug 2013 13:08:04 +0800 [thread overview]
Message-ID: <20130819050803.GA10882@gmail.com> (raw)
In-Reply-To: <CACyNnZONOUy0+OeDriZaSt4OQrR6LzpyJz4Sj8XvMHvxr2u_Xg@mail.gmail.com>
Hello,
On Sun, Aug 18, 2013 at 08:04:20AM +0200, Felipe Monteiro de Carvalho wrote:
> On Sat, Aug 17, 2013 at 3:02 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> > I think part of the problem (besids lots of people being busy and on
> > vacation) is it's not clear what your ext4 reader is going to be used
> > for. As a result it's hard to give advice, not knowing what the
> > requirements are for said reader.
>
> I think that I formulated my question incorrectly. I did not mean
> "please give me advice over my specific application" this time, but
> rather what I wanted was "please tell me a little about these various
> features and also tell me if they are finished or still work in
> progress, etc". Which is precisely what you answered already, so
> thanks a lot =)
>
> > These features aren't quite fully supported yet. The inline data
> > feature is probably closest to be being fully supported, when we
> > release an the next major version of e2fsprogs.
>
> Just for completeness, which version number will that by?
>
> So, I understand that currently mkfs.ext4 cannot generate ext4 file
> systems with this feature, correct?
You need to checkout to e2fsprogs/pu branch. All patches for inline data
are on this branch. BTW, the latest refinement of patches had been sent
to the mailing list [1]. It would be great if you could give it a try.
1. http://comments.gmane.org/gmane.comp.file-systems.ext4/39825
Regards,
- Zheng
>
> Is there any other way to generate a file system with this feature
> with a 3.8 kernel which will work?
>
> Just wondering if I can already start work on this or if I need to wait.
>
> thanks,
> --
> Felipe Monteiro de Carvalho
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-08-19 5:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 15:38 Which features should I implement in my ext4 reader? Felipe Monteiro de Carvalho
2013-08-14 5:06 ` Felipe Monteiro de Carvalho
2013-08-17 6:27 ` Felipe Monteiro de Carvalho
2013-08-17 13:02 ` Theodore Ts'o
2013-08-18 6:04 ` Felipe Monteiro de Carvalho
2013-08-19 5:08 ` Zheng Liu [this message]
2013-08-20 10:16 ` Felipe Monteiro de Carvalho
2013-08-20 10:39 ` Zheng Liu
2013-08-21 12:16 ` Felipe Monteiro de Carvalho
2013-08-23 12:54 ` Felipe Monteiro de Carvalho
2013-08-28 20:09 ` Felipe Monteiro de Carvalho
2013-09-02 9:40 ` Felipe Monteiro de Carvalho
2013-09-02 12:07 ` Zheng Liu
2013-09-02 12:35 ` Felipe Monteiro de Carvalho
2013-09-04 5:35 ` Zheng Liu
2013-09-05 5:25 ` jon ernst
[not found] ` <CAGW2f1FgHZsQbNMyWiD997UZz55y20qHJHryEcMsgpEwecxftA@mail.gmail.com>
2013-09-05 7:04 ` Felipe Monteiro de Carvalho
2013-09-05 7:41 ` Felipe Monteiro de Carvalho
2013-09-02 16:41 ` Darrick J. Wong
2013-08-19 14:03 ` Theodore Ts'o
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=20130819050803.GA10882@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=felipemonteiro.carvalho@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--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 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.