From: Justin Rush <jarush-Ub+6UvMsOfg@public.gmane.org>
To: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: patch for 2.6.36.4
Date: Wed, 24 Aug 2011 06:58:06 -0500 [thread overview]
Message-ID: <DF79D67463342E47A18897C1112AEF644ABB784D94@ESCC1.epicsys.com> (raw)
I am running 2.6.36.4 and I had to apply a few patches to get current hardware working as well as the lio backports so I prefer to stay on this kernel. Is there a 2.6.34.4 patch available? If not, can I make one?
Looking at this helpful human's post, it looks fairly straightforward:
http://comments.gmane.org/gmane.linux.kernel.bcache.devel/24
I checked out both trees, then switched to my branch:
git checkout -b 2.6.36.4
Then created the patch:
git diff linux-2.6 linux-bcache >patch
However, this resulted in a 236MB patch file, which is several orders of magnitude bigger than any other patch I have ever used. Assuming this is even the right way to do it, do I just install it by moving it into my running kernel's source and doing a patch -p0 patch ?
Slightly un-related question:
I want to use this as a cache for two sw raid6 arrays. The raid devices have a bunch of logical volumes carved out of them and those LVs are presented to LIO and served out as iSCSI LUNs. Will bcache serve as a write cache for these devices? My read performance is great, but my random write performance, or write performance in general, really sucks hard.
Justin Rush
next reply other threads:[~2011-08-24 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 11:58 Justin Rush [this message]
[not found] ` <DF79D67463342E47A18897C1112AEF644ABB784D94-ImNGgY1ij29GrYL3PhN6HgC/G2K4zDHf@public.gmane.org>
2011-08-24 17:44 ` patch for 2.6.36.4 Kent Overstreet
[not found] ` <4E553860.4050309-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-08-24 17:56 ` Justin Rush
[not found] ` <DF79D67463342E47A18897C1112AEF644ABB784F12-ImNGgY1ij29GrYL3PhN6HgC/G2K4zDHf@public.gmane.org>
2011-08-24 17:57 ` Kent Overstreet
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=DF79D67463342E47A18897C1112AEF644ABB784D94@ESCC1.epicsys.com \
--to=jarush-ub+6uvmsofg@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 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.