public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ferenc Havasi <havasi@inf.u-szeged.hu>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: linux-mtd@lists.infradead.org, "Zhao, Forrest" <forrest.zhao@intel.com>
Subject: Re: The problem that I didn't think out
Date: Mon, 28 Nov 2005 01:32:35 +0100	[thread overview]
Message-ID: <438A5023.4040503@inf.u-szeged.hu> (raw)
In-Reply-To: <4389B293.3020507@yandex.ru>

Hi Artem,

> Nonetheless, tests should show the worthiness of keys compression. 
> There is obviously a (CPU time) vs. (amount of flash IO) trade-off. 
> Thus, I offer to wait for a JFFS3 prototype and evaluate this. Let's 
> mark this stuff as "to be evaluated".

Yes, I think the same.

>> The big questions are that questions you already thinging on: garbage
>> collection and wear leveling. Without solving them JFFS3 have no nice
>> future. I only would like to say that now we are also thinking on these
>> important problems... and we will write if anything usable found. (I may
>> be better feeling to thinking on someting not alone... :) )
>
> Great! :-)

I was thinking a lot. There is something in my mind, but I have to think 
it over again tomorrow before writing it down.

Be that as it may I have a NAND question, I think you know the answer 
(NAND Guru Artem :) ):
- if there is and erase block aready fulled, is there any possibility to 
mark its pages as obsolated (individually)? Is it allowed to write to 
OOB (or data) area one more? (or write OOB later than the data... or 
similar trick?)
At NOR it is so easy.

Ferenc

  reply	other threads:[~2005-11-28  0:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-25  8:36 The problem that I didn't think out Zhao, Forrest
2005-11-25 11:58 ` Artem B. Bityutskiy
2005-11-27 13:01   ` Ferenc Havasi
2005-11-27 13:20     ` Artem B. Bityutskiy
2005-11-28  0:32       ` Ferenc Havasi [this message]
2005-11-28 10:15         ` Artem B. Bityutskiy
2005-11-28  2:20   ` zhao, forrest
2005-11-28 10:24     ` Artem B. Bityutskiy

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=438A5023.4040503@inf.u-szeged.hu \
    --to=havasi@inf.u-szeged.hu \
    --cc=dedekind@yandex.ru \
    --cc=forrest.zhao@intel.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