From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 an nodes checking
Date: Tue, 28 Sep 2004 20:48:44 +0400 [thread overview]
Message-ID: <415995EC.8010004@yandex.ru> (raw)
In-Reply-To: <1096383492.30942.83.camel@hades.cambridge.redhat.com>
> Yes, he does. The problem is that each time you access a FIFO you update
> its ctime and mtime on the flash... which leads to a _lot_ of nodes,
> only one of which is non-obsolete. That's a problem on NAND flash.
Things are same for regular files. This is from SUSv3 for write() call:
"Upon successful completion, where nbyte is greater than 0, write()
shall mark for update the st_ctime and st_mtime fields of the file"
This is from SUSv3 fore read() call:
"Upon successful completion, where nbyte is greater than 0, read() shall
mark for update the st_atime field of the file, and shall return the
number of bytes read."
What's special with FIFOs ?
Why that's a problem on NAND flash especially ?
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2004-09-28 16:50 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
2004-09-28 14:58 ` David Woodhouse
2004-09-28 16:48 ` Artem B. Bityuckiy [this message]
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=415995EC.8010004@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox