From: "Paul B. Henson" <henson-HInyCGIudOg@public.gmane.org>
To: 'Kent Overstreet' <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: 3.10LTS ok for production?
Date: Tue, 12 Nov 2013 16:21:00 -0800 [thread overview]
Message-ID: <08dd01cee006$3d6de180$b849a480$@acm.org> (raw)
In-Reply-To: <20131109064721.GC30271@kmo-pixel>
> From: Kent Overstreet [mailto:kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org]
> Sent: Friday, November 08, 2013 10:47 PM
>
> Yes - 3.10 LTS (or 3.11) has been what you want to be running for awhile
> now; I've been making sure all the bugfixes get backported quickly.
Cool, thanks for the feedback. I ended up starting with a 3.11.7 kernel
after all, I'm going to play with that and see what happens. I'm looking
forward to the potential support for redundant cache devices within bcache
itself, so I won't have to mirror my two SSDs, but still have redundancy for
writeback and more overall space for read caching. Not sure what the
timeline is for that, but imagine it wouldn't be backported to 3.10.
prev parent reply other threads:[~2013-11-13 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 3:01 3.10LTS ok for production? Paul B. Henson
[not found] ` <20131109030128.GJ5474-eJ6RpuielZ6oHZ9hTG1MgCsmlnnoMqry@public.gmane.org>
2013-11-09 5:29 ` Matthew Patton
[not found] ` <op.w59n7e06f3gqgg-r49W/1Cwd2cba4AQcYcrVKxOck334EZe@public.gmane.org>
2013-11-13 0:17 ` Paul B. Henson
2013-11-09 6:47 ` Kent Overstreet
2013-11-09 7:11 ` Stefan Priebe
[not found] ` <527DE027.2050606-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-11-13 0:21 ` Paul B. Henson
2013-11-13 0:21 ` Paul B. Henson [this message]
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='08dd01cee006$3d6de180$b849a480$@acm.org' \
--to=henson-hinycgiudog@public.gmane.org \
--cc=kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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