From: Guoqing Jiang <gqjiang@suse.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-raid <linux-raid@vger.kernel.org>,
linux-block@vger.kernel.org, shli@kernel.org, neilb@suse.com,
songliubraving@fb.com, pawel.baldysiak@intel.com,
artur.paszkiewicz@intel.com, Jes.Sorensen@redhat.com,
Hannes Reinecke <hare@suse.de>,
colyli@suse.de
Subject: [LSF/MM ATTEND] md raid general discussion
Date: Mon, 16 Jan 2017 14:35:27 +0800 [thread overview]
Message-ID: <587C69AF.5030602@suse.com> (raw)
Hi All,
As you know, Coly has proposed a general md raid discussion. I
would like to attend this discussion, and besides the topics listed
in previous proposal, I think we can talk about improve the test
suite of mdadm to make it more robust (I can share related test
suite which is used for clustered raid).
Also I could share the status of clustered raid about what we have
done and what we can do in the future.
Finally, I'd want to know/discuss about the roadmap of RAID.
Thanks a lot!
Guoqing
reply other threads:[~2017-01-16 6:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=587C69AF.5030602@suse.com \
--to=gqjiang@suse.com \
--cc=Jes.Sorensen@redhat.com \
--cc=artur.paszkiewicz@intel.com \
--cc=colyli@suse.de \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=neilb@suse.com \
--cc=pawel.baldysiak@intel.com \
--cc=shli@kernel.org \
--cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).