From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org
Cc: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [GIT PULL] Bcache fixes for 3.10
Date: Tue, 30 Apr 2013 12:52:14 -0700 [thread overview]
Message-ID: <20130430195214.GH9931@google.com> (raw)
Hey Jens, this is everything I've got ready for 3.10 - there's _still_
one more bug I'm trying to track down.
Andrew - I've got patches that rip out the pkey() and pbtree() macros,
but they're somewhat tied up with some other nontrivial refactorings so
I think I'm going to wait a bit on those.
The following changes since commit cef5279735d3f6f0243e626963e6d5c84efade0a:
bcache: Disable broken btree fuzz tester (2013-04-08 13:33:49 -0700)
are available in the git repository at:
http://evilpiepirate.org/git/linux-bcache.git bcache-for-upstream
for you to fetch changes up to cd66f1f69ed40270bb34e20b25a8111bc72a1b2a:
bcache: Use bd_link_disk_holder() (2013-04-24 13:15:17 -0700)
----------------------------------------------------------------
Kent Overstreet (8):
bcache: Take data offset from the bdev superblock.
bcache: Set ra_pages based on backing device's ra_pages
bcache: Hack around stuff that clones up to bi_max_vecs
bcache: Correctly check against BIO_MAX_PAGES
bcache: Fix merge_bvec_fn usage for when it modifies the bvm
bcache: Make sure blocksize isn't smaller than device blocksize
bcache: Allocator cleanup/fixes
bcache: Use bd_link_disk_holder()
drivers/md/bcache/alloc.c | 74 +++++++++++++-------
drivers/md/bcache/bcache.h | 48 ++++++++++---
drivers/md/bcache/btree.c | 8 +--
drivers/md/bcache/io.c | 35 ++++++----
drivers/md/bcache/request.c | 2 +-
drivers/md/bcache/super.c | 166 +++++++++++++++++++++++++++-----------------
6 files changed, 215 insertions(+), 118 deletions(-)
next reply other threads:[~2013-04-30 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 19:52 Kent Overstreet [this message]
[not found] ` <20130430195214.GH9931-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-05-01 7:26 ` [GIT PULL] Bcache fixes for 3.10 Jens Axboe
2013-05-01 18:54 ` Kent Overstreet
[not found] ` <20130501185450.GA4057-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-05-01 19:05 ` Jens Axboe
[not found] ` <20130501190553.GC7800-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2013-05-01 21:19 ` Kent Overstreet
2013-05-02 6:10 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2013-05-15 7:53 Kent Overstreet
[not found] ` <20130515075302.GA26662-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-05-15 8:06 ` Jens Axboe
[not found] ` <20130515080645.GC3276-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2013-05-15 8:12 ` Kent Overstreet
[not found] ` <20130515081241.GA16030-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-05-15 8:38 ` Jens Axboe
[not found] ` <20130515083851.GH3276-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2013-05-15 13:16 ` Konstantin Ryabitsev
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=20130430195214.GH9931@google.com \
--to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-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