All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: <torvalds@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Core block bits for 4.4-rc
Date: Tue, 3 Nov 2015 17:03:35 -0700	[thread overview]
Message-ID: <20151104000335.GA13194@kernel.dk> (raw)

Hi Linus,

This is the core block pull request for 4.4. I've got a few more topic
branches this time around, some of them will layer on top of the
core+drivers changes and will come in a separate round. So not a huge
chunk of changes in this round. This pull request contains:

- Enable blk-mq page allocation tracking with kmemleak, from Catalin.

- Unused prototype removal in blk-mq from Christoph.

- Cleanup of the q->blk_trace exchange, using cmpxchg instead of two
  xchg()'s, from Davidlohr.

- A plug flush fix from Jeff.

- Also from Jeff, a fix that means we don't have to update shared tag
  sets at init time unless we do a state change. This cuts down boot
  times on thousands of devices a lot with scsi/blk-mq.

- blk-mq waitqueue barrier fix from Kosuke.

- Various fixes from Ming:

        - Fixes for segment merging and splitting, and checks, for
          the old core and blk-mq.

        - Potential blk-mq speedup by marking ctx pending at the end
          of a plug insertion batch in blk-mq.

        - direct-io no page dirty on kernel direct reads.

- A WRITE_SYNC fix for mpage from Roman.

Please pull! Drivers and topic branches coming shortly.


  git://git.kernel.dk/linux-block.git for-4.4/core


----------------------------------------------------------------
Catalin Marinas (1):
      block: kmemleak: Track the page allocations for struct request

Christoph Hellwig (1):
      blk-mq: remove unused blk_mq_clone_flush_request prototype

Davidlohr Bueso (1):
      blktrace: re-write setting q->blk_trace

Jeff Moyer (2):
      block: fix plug list flushing for nomerge queues
      blk-mq: avoid excessive boot delays with large lun counts

Jens Axboe (1):
      Merge tag 'v4.3-rc4' into for-4.4/core

Kosuke Tatsukawa (1):
      blk-mq: fix waitqueue_active without memory barrier in block/blk-mq-tag.c

Ming Lei (7):
      fs: direct-io: don't dirtying pages for ITER_BVEC/ITER_KVEC direct read
      block: setup bi_phys_segments after splitting
      block: avoid to merge splitted bio
      blk-mq: check bio_mergeable() early before merging
      block: check bio_mergeable() early before merging
      blk-mq: fix for trace_block_plug()
      blk-mq: mark ctx as pending at batch in flush plug path

Roman Pen (1):
      fs/mpage.c: forgotten WRITE_SYNC in case of data integrity write

 block/blk-core.c        | 32 ++++++++++++++++--
 block/blk-merge.c       | 32 ++++++++++++++----
 block/blk-mq-tag.c      |  4 +++
 block/blk-mq.c          | 89 ++++++++++++++++++++++++++++++++++---------------
 block/blk-mq.h          |  2 --
 block/blk.h             |  1 +
 block/elevator.c        |  2 +-
 fs/direct-io.c          |  9 +++--
 fs/mpage.c              | 23 ++++++++-----
 kernel/trace/blktrace.c | 16 +++------
 10 files changed, 148 insertions(+), 62 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2015-11-04  0:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151104000335.GA13194@kernel.dk \
    --to=axboe@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linuxfoundation.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.