public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Wheeler <bcache@lists.ewheeler.net>
To: Jens Axboe <axboe@kernel.dk>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
	linux-bcache@vger.kernel.org, dave@stgolabs.net,
	linux-kernel@vger.kernel.org, Kai Krakow <kai@kaishome.de>,
	Wido den Hollander <wido@widodh.nl>,
	Emmanuel Florac <eflorac@intellique.com>,
	Hans van den Bogert <hansbogert@gmail.com>,
	"Jens-U. Mozdzen" <jmozdzen@nde.ag>
Subject: [PULL] bcache: based on for-4.10/block, multiple updates
Date: Tue, 6 Dec 2016 11:47:41 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.11.1612061145430.13402@mail.ewheeler.net> (raw)
In-Reply-To: <6bda49c5-5ed8-939f-aab3-faa9c8127ff0@kernel.dk>

Hello Jens,

Please pull for 4.10:

Thank you!

This pull request is based on the git.kernel.dk for-4.10/block branch:

The following changes since commit 333ba053d145d6f9152f6b0311a345b876f0fed1:

  lightnvm: transform target get/set bad block (2016-11-29 12:12:51 -0700)

are available in the git repository at:

  https://bitbucket.org/ewheelerinc/linux.git for-4.10-block-bcache-updates

for you to fetch changes up to 951c0a8cc489aca1c68d80e5aaa576cd7e511191:

  bcache: partition support: add 16 minors per bcacheN device (2016-12-06 10:13:24 -0800)

----------------------------------------------------------------
Eric Wheeler (4):
      bcache: introduce per-process ioprio-based bypass/writeback hints
      bcache: documentation for ioprio cache hinting
      bcache: update bio->bi_opf bypass/writeback REQ_ flag hints
      bcache: partition support: add 16 minors per bcacheN device

Kent Overstreet (1):
      bcache: Make gc wakeup sane, remove set_task_state()

 Documentation/bcache.txt      | 80 +++++++++++++++++++++++++++++++++++++++++++
 drivers/md/bcache/bcache.h    |  7 ++--
 drivers/md/bcache/btree.c     | 39 +++++++++++----------
 drivers/md/bcache/btree.h     |  3 +-
 drivers/md/bcache/request.c   | 31 +++++++++++++++--
 drivers/md/bcache/super.c     |  7 +++-
 drivers/md/bcache/sysfs.c     | 71 ++++++++++++++++++++++++++++++++++++++
 drivers/md/bcache/writeback.c |  8 +++++
 drivers/md/bcache/writeback.h | 27 ++++++++++++++-
 9 files changed, 245 insertions(+), 28 deletions(-)

  parent reply	other threads:[~2016-12-06 19:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27 23:27 [PULL] bcache: multiple updates Eric Wheeler
2016-10-28  1:12 ` Jens Axboe
2016-10-30  1:32   ` Eric Wheeler
2016-10-30  3:44     ` Davidlohr Bueso
2016-10-30 14:00     ` Kent Overstreet
2016-10-30 15:01       ` Jens Axboe
2016-11-01  2:35         ` Eric Wheeler
2016-12-06 19:47         ` Eric Wheeler [this message]
2016-12-15  1:50           ` [PULL] bcache: based on for-4.10/block, " Eric Wheeler
2016-12-15  4:47             ` Jens Axboe
2017-01-31 19:14               ` Eric Wheeler
2017-01-31 19:27                 ` Jens Axboe
2017-01-31 23:17                   ` Eric Wheeler
2017-02-28  2:00               ` 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=alpine.LRH.2.11.1612061145430.13402@mail.ewheeler.net \
    --to=bcache@lists.ewheeler.net \
    --cc=axboe@kernel.dk \
    --cc=dave@stgolabs.net \
    --cc=eflorac@intellique.com \
    --cc=hansbogert@gmail.com \
    --cc=jmozdzen@nde.ag \
    --cc=kai@kaishome.de \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wido@widodh.nl \
    /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