From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Nicolas Pitre <nico@cam.org>
Cc: Alexander Belyakov <alexander.belyakov@intel.com>,
linux-mtd@lists.infradead.org, "Kutergin,
Timofey" <timofey.kutergin@intel.com>,
"Korolev, Alexey" <alexey.korolev@intel.com>
Subject: Re: [PATCH/RFC] Linux MTD striping middle layer
Date: Wed, 22 Mar 2006 11:58:29 +0300 [thread overview]
Message-ID: <442111B5.6090308@yandex.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0603211434261.3631@localhost.localdomain>
Nicolas Pitre wrote:
>>Why? I don't see any thing bad with having 3*128KiB eraseblock size...
> I agree with you ....... as long as someone is willing to audit all MTD
> client code to certify that no assumption about erase block sizes being
> a power of 2 is present.
Well, there is no much client code. JFFS2 is happy with this size. If
some client is not happy, this is its problems. This client just has to
be fixed or not use striping with non-power-of-two devices. Indeed,
striping is a distinct layer and is not compulsory to use.
I don't see any reason in prohibiting striping 3 devices, or 5 devices.
Just because power of 2 is digits are widely used is not a serious argument.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2006-03-22 8:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 12:36 [PATCH/RFC] Linux MTD striping middle layer Belyakov, Alexander
2006-03-21 14:01 ` Vitaly Wool
2006-03-21 14:41 ` Alexander Belyakov
2006-03-21 15:11 ` Vitaly Wool
2006-03-22 9:36 ` Alexander Belyakov
2006-03-21 15:37 ` Jörn Engel
2006-03-21 16:37 ` Thomas Gleixner
2006-03-21 15:36 ` Nicolas Pitre
2006-03-21 15:09 ` Artem B. Bityutskiy
2006-03-21 18:11 ` Alexander Belyakov
2006-03-21 18:57 ` Artem B. Bityutskiy
2006-03-21 19:37 ` Nicolas Pitre
2006-03-21 20:24 ` Jörn Engel
2006-03-22 8:58 ` Artem B. Bityutskiy [this message]
2006-03-22 14:40 ` Alexander Belyakov
2006-03-22 14:47 ` Artem B. Bityutskiy
2006-03-22 15:10 ` Alexander Belyakov
2006-03-22 15:15 ` Artem B. Bityutskiy
2006-03-22 15:39 ` Alexander Belyakov
2006-03-22 15:45 ` Vitaly Wool
2006-03-22 16:23 ` Alexander Belyakov
2006-03-22 16:30 ` Artem B. Bityutskiy
2006-03-22 19:25 ` Vitaly Wool
2006-03-22 19:40 ` Nicolas Pitre
2006-03-23 10:10 ` Vitaly Wool
2006-03-22 15:51 ` Artem B. Bityutskiy
2006-03-22 9:39 ` Alexander Belyakov
2006-03-22 9:52 ` Artem B. Bityutskiy
2006-03-22 10:26 ` Alexander Belyakov
2006-03-22 10:51 ` Artem B. Bityutskiy
2006-03-22 13:35 ` Alexander Belyakov
2006-03-22 14:40 ` Artem B. Bityutskiy
2006-03-22 16:19 ` Artem B. Bityutskiy
2006-03-22 16:23 ` Artem B. Bityutskiy
2006-03-22 17:17 ` Nicolas Pitre
2006-03-22 17:28 ` Artem B. Bityutskiy
2006-03-22 17:50 ` Nicolas Pitre
2006-03-21 19:08 ` Artem B. Bityutskiy
2006-03-22 9:57 ` Alexander Belyakov
2006-03-22 10:23 ` Artem B. Bityutskiy
2006-03-22 17:08 ` Artem B. Bityutskiy
2006-03-22 17:23 ` Nicolas Pitre
2006-03-23 9:39 ` Alexander Belyakov
2006-03-23 14:23 ` Nicolas Pitre
2006-03-23 14:45 ` Alexander Belyakov
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=442111B5.6090308@yandex.ru \
--to=dedekind@yandex.ru \
--cc=alexander.belyakov@intel.com \
--cc=alexey.korolev@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.org \
--cc=timofey.kutergin@intel.com \
/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