From: Johannes Thumshirn <jthumshirn@suse.de>
To: Eric Wheeler <bcache@lists.ewheeler.net>,
Kent Overstreet <kmo@daterainc.com>
Cc: linux-bcache@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>,
Joshua Schmid <jschmid@suse.com>,
Al Viro <viro@zeniv.linux.org.uk>, Takashi Iwai <tiwai@suse.de>,
Zheng Liu <gnehzuil.liu@gmail.com>,
manover@gmail.com, g2p.code@gmail.com,
stefan.bader@canonical.com, linux-kernel@vger.kernel.org
Subject: Re: [PULL REQUEST]: bcache stability patches
Date: Wed, 02 Dec 2015 13:18:35 +0100 [thread overview]
Message-ID: <1449058715.3103.82.camel@suse.de> (raw)
In-Reply-To: <alpine.LRH.2.11.1511291750520.5445@mail.ewheeler.net>
On Sun, 2015-11-29 at 20:13 -0800, Eric Wheeler wrote:
> Hello all,
>
> Please pull this bcache branch with stability patches and see if it fixes
> any issue that you might have! If you have stability patches (*that you
> have tested*) which are not part of this branch, then please forward them
> so they can be included.
>
> We have been using bcache with great performance and stability for over a
> year; it is the best SSD caching mechanism that we have found for our
> workload.
>
> I've been collecting these fixes for a while now and just put them up on
> github so they can be easily merged. I continue to see mailing list
> discussions about problems that users are having which these patches
> address, so hopefully we can get these merged:
>
> https://github.com/ewheelerinc/linux/commits/bcache-patches-for-3.17
> git add remote ewheelerinc https://github.com/ewheelerinc/linux.git
> git fetch ewheelerinc
> git merge ewheelerinc/bcache-patches-for-3.17
>
> This branch is from a clone of Linus's tree circa 3.17-rc so git merge
> should bring this in cleanly to any later branch. This will merge cleanly
> into kernel.org longerm versions v4.1.13 and v3.18.24. The original
> author is cited in each commit; you are being Cc'ed in this email if you
> are an author on any of these patches or are part of a mailing list thread
> indicating problems that this pull may fix.
I just did a test merge on the patches against today's master and I had no
merge conflicts. The overall diff looks reasonable as well and it builds w/o
any warnings.
Just pulling them straight in won't be a good idea though, as the From: always
points to Eric, that needs to be fixed up (but that's all just mechanics).
>
> Each commit includes `Cc: stable@vger.kernel.org` so if they get pulled
> into mainline we will see bcache stable on the newer LTS branches of
> kernel.org.
>
> This git branch includes patches that have been collected and tested by
> Denis Bychkov from his post on 2015-09-16 with one exception: the
> refill_dirty() patch has been updated to the latest stable version which
> Kent posted the next day. The refill_dirty patch addresses issues when
> bcache is backed by raid5/6 md's causing
> queue_limits->partial_stripes_expensive to be nonzero.
>
>
> Kent,
>
> Can this be sent to Jens for a pull into mainline? If you can give your
> OK on this patchset then I'll approach Jens and see if he can pull this
> in. Maybe Cc him in your response.
>
> If there's anything in here that you would like to omit or change from
> this pull then let me know and I'll rebase.
>
> Thanks!
>
> -Eric
>
Kent, can you please merge these patches? There are people out there actually
using bcache and these patches aren't just cosmetics.
Thanks a lot for collecting these patches Eric.
Johannes
>
>
> --
> Eric Wheeler, President eWheeler, Inc. dba Global Linux Security
> 888-LINUX26 (888-546-8926) Fax: 503-716-3878 PO Box 25107
> www.GlobalLinuxSecurity.pro ; Linux since 1996! Portland, OR 97298
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2015-12-02 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.2.11.1511291750520.5445@mail.ewheeler.net>
2015-12-02 12:18 ` Johannes Thumshirn [this message]
2015-12-05 7:52 ` [PULL REQUEST]: bcache stability patches Eric Wheeler
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=1449058715.3103.82.camel@suse.de \
--to=jthumshirn@suse.de \
--cc=bcache@lists.ewheeler.net \
--cc=g2p.code@gmail.com \
--cc=gnehzuil.liu@gmail.com \
--cc=jschmid@suse.com \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manover@gmail.com \
--cc=stefan.bader@canonical.com \
--cc=tiwai@suse.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wenqing.lz@taobao.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