From: Alexander Belyakov <alexander.belyakov@intel.com>
To: dedekind@infradead.org
Cc: "Korolev, Alexey" <alexey.korolev@intel.com>,
linux-mtd@lists.infradead.org, "Kutergin,
Timofey" <timofey.kutergin@intel.com>
Subject: Re: [PATCH/RFC] Linux MTD striping middle layer
Date: Tue, 21 Mar 2006 21:11:10 +0300 [thread overview]
Message-ID: <442041BE.9070407@intel.com> (raw)
In-Reply-To: <1142953764.13740.0.camel@sauron.oktetlabs.ru>
Artem,
please find my answers below.
Artem B. Bityutskiy wrote:
> Hello Alexander,
>
> I have basic questions as I haven't grasped your concepts. Note, I'm not
> an expert in RAID, so please, bother to explain basic notions as well.
>
>
> Why can't I have 3 or 5 chips and enable striping?
>
Striped mtd device erasesize is an erasesize of subdevice multiplied by
number of subdevices (in case of equal erasesize subdevices). As
erasesize is commonly considered as a power-of-2 number it is not good
idea to use 3, 5, etc devices.
>
>
>> cmdline_parm="<stripedef>[;<stripedef>]"
>> <stripedef> :=
>>
> <stripename>(<interleavesize>):<subdevname>.<subdevname>
>
>> Example:
>> insmod mtdstripe.ko
>> cmddline_parm="stripe1(128):vol1.vol3;stripe2(128):vol2.vol4
>> Note: you should use '.' as a delimiter for subdevice names here.
>>
> Err, please, define the "subdevice" notion. And what is vol1, vol2, etc?
>
Subdevices are mtd devices which participate in creation of striped mtd
device (superdevice). vol1, vol2 here are the names of subdevices
assigned on partitioning stage (for example) by the following part of
kernel configuration string:
CONFIG_CMDLINE="..........
mtdparts=flash1:512k(blob)ro,2m(kernel)ro,16m(root),16m(vol1);flash2:16m(vol2),8m(vol3)
........."
> Please, describe the model of the striped MTD device from user's
> perspective. I understand MTD concatenation. It just merges several MTD
> devices to one larger MTD device.
>
If user has several independent chips (of the same type) in system he
can stripe them to get performance boost.
> May I consider your striping as another type of MTD concatenation layer
> which concatenates MTD devices by means of interleaving eraseblocks?
>
Your interpretation is similar to JBOD (concatenation) and RAID0
(striping) comparison. Yes in case of striping we also get a larger
device as for concatenation. But the interleave size may differ from
subdevices erasesize. Actually interleave size is significantly smaller
than erasesize.
> Suppose my interleave value is 512. Suppose the interleaved MTD
> device name is mtd7 and it concatenates 2 other MTD devices. What
> happens if:
>
> 1. I write 512 bytes at offset 0 of eraseblock 0 of mtd7
>
These 512 bytes will be written at first subdevice at offset 0
> 2. I write 512 bytes at offset 512 of eraseblock 0 of mtd7
>
These 512 bytes will be written at second subdevice at offset 0
> 3. I write 512 bytes at offset 1024 of eraseblock 0 of mtd7
>
These 512 bytes will be written at first subdevice at offset 512
> 4. I erase eraseblock 0 of mtd7
>
In simple case eraseblock 0 on both subdevices 1 and 2 will be erased
Thanks,
Alexander Belyakov
next prev parent reply other threads:[~2006-03-21 18:38 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 [this message]
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
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=442041BE.9070407@intel.com \
--to=alexander.belyakov@intel.com \
--cc=alexey.korolev@intel.com \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.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