From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: 4K block size question
Date: Wed, 20 Oct 2004 15:17:14 +0400 [thread overview]
Message-ID: <4176493A.5080003@yandex.ru> (raw)
In-Reply-To: <1098270013.3872.83.camel@baythorne.infradead.org>
> By writing nodes which don't cover a full 4KiB and hence aren't
> pristine.
Thanks.
By the way, what do you (and other JFFS2 folks) think about very big
nodes of size = block size? I'm going to create such a big inode
checkpoints. Is it OK? Are there some reasons not to do so and split
them into several smaller nodes?
Thanks.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2004-10-20 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 10:57 4K block size question Artem B. Bityuckiy
2004-10-20 11:00 ` David Woodhouse
2004-10-20 11:17 ` Artem B. Bityuckiy [this message]
2004-10-20 11:21 ` David Woodhouse
2004-10-20 11:59 ` Artem B. Bityuckiy
2004-10-21 11:58 ` Artem B. Bityuckiy
2004-10-21 12:08 ` David Woodhouse
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=4176493A.5080003@yandex.ru \
--to=abityuckiy@yandex.ru \
--cc=dwmw2@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 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.