From: Dongsheng Yang <dongsheng.yang@easystack.cn>
To: dedekind1@gmail.com, Richard Weinberger <richard@nod.at>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: fabf@skynet.be, jesper.nilsson@axis.com,
Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
linux-cris-kernel@axis.com, shengyong1@huawei.com,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Dongsheng Yang <dongsheng081251@gmail.com>,
dmitry.torokhov@gmail.com, dooooongsheng.yang@gmail.com,
jschultz@xes-inc.com, starvik@axis.com, mtownsend1973@gmail.com,
linux-mtd@lists.infradead.org,
Colin King <colin.king@canonical.com>,
asierra@xes-inc.com, Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: MTD RAID
Date: Fri, 19 Aug 2016 18:38:53 +0800 [thread overview]
Message-ID: <57B6E1BD.1060707@easystack.cn> (raw)
In-Reply-To: <1471602645.2662.10.camel@gmail.com>
Artem
On 08/19/2016 06:30 PM, Artem Bityutskiy wrote:
> On Fri, 2016-08-19 at 11:47 +0200, Richard Weinberger wrote:
>> So, what you propose as MTD RAID is not really RAID.
>> RAID is about redundant disks. i.e. you can replace them upon
>> failure.
Yes, we can replace it, but we can add/delete devices in btrfs in different
RAID level by :
btrfs device add/delete <device>
That's software raid, similar with Software raid for block device in md.
Yang
>> The problem you address is combining multiple chips.
>> IOW an SSD emulated in software.
> I think this should either be a very close analog of RAID or the word
> "RAID" should not be used at all. Everyone will be confused otherwise.
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2016-08-19 10:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+qeAOpuZ0CXZP8tCWdhoVvTEKAw26gtz63-UJmQ4XLSXAd=Yg@mail.gmail.com>
2016-08-19 6:49 ` MTD RAID Boris Brezillon
2016-08-19 7:08 ` Dongsheng Yang
2016-08-19 7:15 ` Dongsheng Yang
2016-08-19 7:28 ` Dongsheng Yang
2016-08-19 8:20 ` Boris Brezillon
[not found] ` <CA+qeAOrSAi9uTHGCi-5cAJpM_O45oJUihNP-rHHa1FWL7_ZKHQ@mail.gmail.com>
2016-08-19 9:37 ` Boris Brezillon
2016-08-19 10:22 ` Dongsheng Yang
2016-08-19 11:36 ` Boris Brezillon
[not found] ` <57B6CC7B.1060208@easystack.cn>
2016-08-19 9:47 ` Richard Weinberger
2016-08-19 10:30 ` Dongsheng Yang
2016-08-19 10:30 ` Artem Bityutskiy
2016-08-19 10:38 ` Dongsheng Yang [this message]
[not found] ` <AL*AZwAyAecQSM1UjjjNxao0.3.1471605640762.Hmail.dongsheng.yang@easystack.cn>
2016-08-19 11:55 ` Boris Brezillon
2016-08-22 4:01 ` Dongsheng Yang
2016-08-22 7:09 ` Boris Brezillon
[not found] ` <57BA6FFA.6000601@easystack.cn>
2016-08-22 7:07 ` Boris Brezillon
2016-08-22 7:27 ` Artem Bityutskiy
[not found] ` <CAAp9bSh-geStbHpA6+vYdLfNLcinWkfVLOGmX4kdRbja+d2MdA@mail.gmail.com>
2016-08-22 14:54 ` Artem Bityutskiy
2016-08-22 15:30 ` David Woodhouse
2016-08-23 3:44 ` Dongsheng Yang
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=57B6E1BD.1060707@easystack.cn \
--to=dongsheng.yang@easystack.cn \
--cc=ard.biesheuvel@linaro.org \
--cc=asierra@xes-inc.com \
--cc=boris.brezillon@free-electrons.com \
--cc=colin.king@canonical.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dongsheng081251@gmail.com \
--cc=dooooongsheng.yang@gmail.com \
--cc=dwmw2@infradead.org \
--cc=fabf@skynet.be \
--cc=jesper.nilsson@axis.com \
--cc=jschultz@xes-inc.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mtownsend1973@gmail.com \
--cc=richard@nod.at \
--cc=shengyong1@huawei.com \
--cc=starvik@axis.com \
--cc=yangds.fnst@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.