From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: Josh Boyer <jdub@us.ibm.com>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: JFFS2 an nodes checking
Date: Tue, 28 Sep 2004 18:47:33 +0400 [thread overview]
Message-ID: <41597985.3080803@yandex.ru> (raw)
In-Reply-To: <1096381863.17956.12.camel@weaponx.rchland.ibm.com>
> Yes, large files are bad, but aren't the only source of such a time
> delay. IIRC, the problem is really just a matter of the number of nodes
> per file. So couldn't you have a small file with a large number of
> writes within that file that has the same effect? (Until the obsoleted
> nodes are actually deleted that is.)
>
> I'm thinking of fifos here too...
>
> josh
>
I suppose you don't mean the Unix FIFO file type (like block device,
socket, etc).
Yes, if we have a file with a lot of small nodes, we will read node
headers anyway.
This case won't be optimized very much if we don't check the data CRC.
But after the GC process this file will be optimized and split on 4K
pieces :-)
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2004-09-28 14:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 12:29 JFFS2 an nodes checking Artem B. Bityuckiy
2004-09-28 12:37 ` David Woodhouse
2004-09-28 13:17 ` Artem B. Bityuckiy
2004-09-28 13:22 ` David Woodhouse
2004-09-28 13:37 ` Artem B. Bityuckiy
2004-09-28 13:45 ` David Woodhouse
2004-09-28 13:57 ` Artem B. Bityuckiy
2004-09-28 14:04 ` David Woodhouse
2004-09-28 14:26 ` Artem B. Bityuckiy
2004-09-28 14:37 ` David Woodhouse
2004-09-28 14:58 ` Artem B. Bityuckiy
2004-09-28 15:04 ` David Woodhouse
2004-09-28 14:31 ` Josh Boyer
2004-09-28 14:47 ` Artem B. Bityuckiy [this message]
2004-09-28 14:58 ` David Woodhouse
2004-09-28 16:48 ` Artem B. Bityuckiy
2004-09-28 16:57 ` Josh Boyer
2004-09-28 16:58 ` David Woodhouse
2004-09-28 17:15 ` Artem B. Bityuckiy
2004-09-28 18:24 ` Josh Boyer
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=41597985.3080803@yandex.ru \
--to=abityuckiy@yandex.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