From: Jared Hulbert <jaredeh@gmail.com>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: JFFS3 & deletion dirents RFC
Date: Wed, 23 Mar 2005 17:27:36 -0800 [thread overview]
Message-ID: <6934efce0503231727f7234f6@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503221406120.5581@phoenix.infradead.org>
Forgive me if my ignorance is obvious...
Are there any implications to non-dirent nodes? Shouldn't this speed
up the GC, mount time for any node? If not then the version field for
non-dirent nodes is utterly wasted, right? If the version field is
wasted for all non-dirent nodes (in other words, most nodes) then it
seems like a bad idea to add a WORD or DWORD to each node. If there is
a way to make version field only apply to dirent nodes then it would
be much better, of course that sounds ugly without even thinking it
through too far.
next prev parent reply other threads:[~2005-03-24 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 14:06 JFFS3 & deletion dirents RFC Artem B. Bityuckiy
2005-03-24 1:27 ` Jared Hulbert [this message]
2005-03-24 9:18 ` Artem B. Bityuckiy
2005-03-24 22:01 ` Jared Hulbert
2005-03-25 8:36 ` Artem B. Bityuckiy
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=6934efce0503231727f7234f6@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.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