From: Artem Bityuckiy <dedekind@oktetlabs.ru>
To: Josh Boyer <jdub@us.ibm.com>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: inode checkpoints
Date: Mon, 04 Oct 2004 17:56:29 +0400 [thread overview]
Message-ID: <4161568D.3060605@oktetlabs.ru> (raw)
In-Reply-To: <1096897195.22034.23.camel@weaponx.rchland.ibm.com>
>
>
> I agree that these changes will benefit NAND the most, but they are also
> valuable for all flashes.
>
> Say I have a 16 MiB file on my NOR flash. When a stat or open is done,
> iget is called, which calls readinode, which then goes and reads all the
> nodes off of the flash to build up the inode information. I've seen
> that take upwards of 2 seconds, just because of the number of data nodes
> that have to be read.
>
> Now, same situation, but I have a checkpoint node out there. I don't
> have to read _all_ the data nodes because the checkpoint gives me a
> snapshot of at least some of them, right?
>
> Or maybe I am extending your idea a bit further than what you
> intended...
>
> josh
>
You are right in general. I would like to say that the NAND ICPs idea is
*superset* for NOR ICP idea, not vice versa... (ICP=inode check point)
But I believe the NOR ICPs shouldn't be implemented together with NAND
cips since NOR ICPs are much simpler. For example, the need bych simpler
data structures, algorithms, etc. I dont think it is a good Idea to have
hunderds of #ifdefs ...
--
Best regards, Artem B. Bityuckiy
Oktet Labs (St. Petersburg), Software Engineer.
+78124286709 (office) +79112449030 (mobile)
E-mail: dedekind@oktetlabs.ru, web: http://www.oktetlabs.ru
next prev parent reply other threads:[~2004-10-04 13:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 10:14 inode checkpoints Artem Bityuckiy
2004-10-04 10:22 ` David Woodhouse
2004-10-04 10:36 ` [OBORONA-SPAM] " Artem B. Bityuckiy
2004-10-04 12:34 ` Josh Boyer
2004-10-04 13:07 ` Artem B. Bityuckiy
2004-10-04 13:18 ` David Woodhouse
2004-10-04 13:32 ` Artem B. Bityuckiy
2004-10-04 13:46 ` Artem B. Bityuckiy
2004-10-04 14:18 ` Artem B. Bityuckiy
2004-10-04 14:23 ` David Woodhouse
2004-10-04 15:07 ` Artem B. Bityuckiy
2004-10-05 14:07 ` Artem B. Bityuckiy
2004-10-05 16:45 ` David Woodhouse
2004-10-05 17:20 ` Josh Boyer
2004-10-06 9:07 ` Artem B. Bityuckiy
2004-10-09 11:45 ` Artem B. Bityuckiy
2004-10-09 11:58 ` Artem B. Bityuckiy
2004-10-09 13:01 ` Artem B. Bityuckiy
2004-10-09 14:48 ` Artem B. Bityuckiy
2004-10-09 13:22 ` Artem B. Bityuckiy
2004-10-04 11:44 ` Artem Bityuckiy
2004-10-04 12:36 ` Josh Boyer
2004-10-04 12:43 ` David Woodhouse
2004-10-04 13:26 ` [OBORONA-SPAM] " Artem B. Bityuckiy
2004-10-04 13:39 ` Josh Boyer
2004-10-04 13:56 ` Artem Bityuckiy [this message]
2004-10-04 14:06 ` Artem B. Bityuckiy
2004-10-04 14:17 ` Josh Boyer
2004-10-04 14:22 ` 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=4161568D.3060605@oktetlabs.ru \
--to=dedekind@oktetlabs.ru \
--cc=dwmw2@infradead.org \
--cc=jdub@us.ibm.com \
--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