From: "Artem B. Bityuckiy" <dedekind@oktetlabs.ru>
To: Zoltan Sogor <weth@inf.u-szeged.hu>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mounting jffs2
Date: Tue, 26 Apr 2005 17:51:01 +0400 [thread overview]
Message-ID: <426E4745.5050606@oktetlabs.ru> (raw)
In-Reply-To: <426E439A.2050301@inf.u-szeged.hu>
Hello Zoltan,
> Read:
> If you want to read an inode then the kernel calls jffs2_do_read_inode()
> to get the inode.
But if I don't want? There are thousands of inodes and I don't have to
read them all. What then? Will GC move dirt along with valid data? Will
I see fewer free space then there is actually present? I suppose yes and
this is incorrect.
--
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:[~2005-04-26 13:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 13:25 mounting jffs2 Sergei Sharonov
2005-04-13 13:50 ` Artem B. Bityuckiy
2005-04-13 14:22 ` Sergei Sharonov
2005-04-13 15:02 ` Artem B. Bityuckiy
2005-04-13 17:51 ` Sergei Sharonov
2005-04-14 8:41 ` Artem B. Bityuckiy
2005-04-14 12:39 ` Sergei Sharonov
2005-04-14 13:11 ` Artem B. Bityuckiy
2005-04-14 14:15 ` Sergei Sharonov
2005-04-14 15:18 ` Artem B. Bityuckiy
2005-04-13 15:18 ` Artem B. Bityuckiy
2005-04-14 20:39 ` Sergei Sharonov
2005-04-14 9:01 ` Ferenc Havasi
2005-04-14 9:15 ` Artem B. Bityuckiy
2005-04-20 14:59 ` Sergei Sharonov
2005-04-20 15:20 ` Artem B. Bityuckiy
2005-04-20 16:34 ` Sergei Sharonov
2005-04-21 7:48 ` Artem B. Bityuckiy
2005-04-21 14:30 ` Ferenc Havasi
2005-04-21 15:31 ` Artem B. Bityuckiy
2005-04-26 13:35 ` Zoltan Sogor
2005-04-26 13:51 ` Artem B. Bityuckiy [this message]
2005-04-27 9:39 ` Zoltan Sogor
2005-04-21 15:34 ` Sergei Sharonov
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=426E4745.5050606@oktetlabs.ru \
--to=dedekind@oktetlabs.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=weth@inf.u-szeged.hu \
/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