From: Song Liu <song@kernel.org>
To: Xiaosong Ma <xma@qf.org.qa>
Cc: linux-raid <linux-raid@vger.kernel.org>,
姜天洋 <ty-jiang18@mails.tsinghua.edu.cn>,
"Guangyan Zhang" <gyzh@tsinghua.edu.cn>,
wei-jy19@mails.tsinghua.edu.cn
Subject: Re: Fw: some questions about uploading a Linux kernel driver
Date: Thu, 30 Apr 2020 00:10:27 -0700 [thread overview]
Message-ID: <CAPhsuW7e-xMNbk5ZJw2XQ3KSnnPiN5gwwR4hdMMhyjjVNRnfkQ@mail.gmail.com> (raw)
In-Reply-To: <CAKm37QWKVcPkF0fXKk2499CsYXfU3aMuMWgwa8Nk9HFzVxG7CA@mail.gmail.com>
Hi Xiaosong,
On Wed, Apr 22, 2020 at 5:26 AM Xiaosong Ma <xma@qf.org.qa> wrote:
>
> Dear Song,
>
> This is Xiaosong Ma from Qatar Computing Research Institute. I am
> writing to follow up with the questions posed by a co-author from
> Tsinghua U, regarding upstreaming our alternative md implementation
> that is designed to significantly reduce SSD RAID latency (both median
> and tail) for large SSD pools (such as 20-disk or more).
>
> We read the Linux kernel upstreaming instructions, and believe that
> our implementation has excellent separability from the current code
> base (as a plug-and-play module with identical interfaces as md).
Plug-and-play is not the key for upstream new code/module. There are
some other keys to consider:
1. Why do we need it? (better performance is a good reason here).
2. What's the impact on existing users?
3. Can we improve existing code to achieve the same benefit?
> Meanwhile, we wonder whether there are standard test cases or
> preferred applications that we should test our system with, before
> doing code cleaning up. Your guidance is much appreciated.
For testing, "mdadm test" is a good starting point (if it works here).
We also need data integrity tests and stress tests.
Thanks,
Song
next prev parent reply other threads:[~2020-04-30 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a7c0aba219642de8b3f1cc680d53d85@AM0P193MB0754.EURP193.PROD.OUTLOOK.COM>
2020-04-22 12:26 ` Fwd: Fw: some questions about uploading a Linux kernel driver Xiaosong Ma
2020-04-24 8:24 ` some questions about uploading a Linux kernel driver FusionRAID Paul Menzel
2020-04-30 7:10 ` Song Liu [this message]
[not found] ` <1b9dc66b2afd49d1bc260691e62858fc@AM0P193MB0754.EURP193.PROD.OUTLOOK.COM>
2020-05-09 10:25 ` Fw: some questions about uploading a Linux kernel driver Xiaosong Ma
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=CAPhsuW7e-xMNbk5ZJw2XQ3KSnnPiN5gwwR4hdMMhyjjVNRnfkQ@mail.gmail.com \
--to=song@kernel.org \
--cc=gyzh@tsinghua.edu.cn \
--cc=linux-raid@vger.kernel.org \
--cc=ty-jiang18@mails.tsinghua.edu.cn \
--cc=wei-jy19@mails.tsinghua.edu.cn \
--cc=xma@qf.org.qa \
/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).