mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: Jens Axboe <axboe@kernel.dk>, linux-kernel@vger.kernel.org
Cc: drbd-dev@lists.linbit.com
Subject: [PATCH 0/9] DRBD updates for 3.18
Date: Thu, 11 Sep 2014 14:29:04 +0200	[thread overview]
Message-ID: <1410438553-30440-1-git-send-email-philipp.reisner@linbit.com> (raw)

Hi Jens,

please consider to put these patches into your (future) for-3.18/drivers
branch. I have posted it for review on August 28. It consists mainly of
minor cleanups, and an important performance improvement. With that
DRBD was seen to write with 160k IOPS, on SSDs.

You may take the patches from this posting, or pull them from
http://git.drbd.org/linux-2.6-drbd.git for-3.18-rc1
the branch there is based on Linux 3.17-rc4.

Andreas Gruenbacher (5):
  drbd: Use better variable names
  drbd: Use consistent names for all the bi_end_io callbacks
  drbd: Avoid inconsistent locking warning
  drbd: Get rid of the __no_warn and __cond_lock macros
  drbd: Get rid of the WORK_PENDING macro

Lars Ellenberg (2):
  drbd: Improve asender performance
  drbd: reduce lock contention in drbd_worker

Philipp Marek (1):
  drbd: Remove superfluous newline from "resync_extents" debugfs entry.

Philipp Reisner (1):
  drbd: Add missing newline in resync progress display in /proc/drbd

 drivers/block/drbd/drbd_actlog.c   |  4 +--
 drivers/block/drbd/drbd_bitmap.c   |  6 ++---
 drivers/block/drbd/drbd_debugfs.c  |  2 +-
 drivers/block/drbd/drbd_int.h      | 19 +++++++-------
 drivers/block/drbd/drbd_main.c     | 28 ++++++++++----------
 drivers/block/drbd/drbd_proc.c     |  4 ++-
 drivers/block/drbd/drbd_receiver.c | 52 +++++++++++++++++++++-----------------
 drivers/block/drbd/drbd_req.c      |  2 +-
 drivers/block/drbd/drbd_state.c    | 18 ++++++-------
 drivers/block/drbd/drbd_worker.c   | 51 +++++++++++++++----------------------
 10 files changed, 93 insertions(+), 93 deletions(-)

-- 
1.9.1


             reply	other threads:[~2014-09-11 12:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 12:29 Philipp Reisner [this message]
2014-09-11 12:29 ` [PATCH 1/9] drbd: Use better variable names Philipp Reisner
2014-09-11 12:29 ` [PATCH 2/9] drbd: Use consistent names for all the bi_end_io callbacks Philipp Reisner
2014-09-11 12:29 ` [PATCH 3/9] drbd: Remove superfluous newline from "resync_extents" debugfs entry Philipp Reisner
2014-09-11 12:29 ` [PATCH 4/9] drbd: Avoid inconsistent locking warning Philipp Reisner
2014-09-11 12:29 ` [PATCH 5/9] drbd: Get rid of the __no_warn and __cond_lock macros Philipp Reisner
2014-09-11 12:29 ` [PATCH 6/9] drbd: Get rid of the WORK_PENDING macro Philipp Reisner
2014-09-11 12:29 ` [PATCH 7/9] drbd: Improve asender performance Philipp Reisner
2014-09-11 12:29 ` [PATCH 8/9] drbd: reduce lock contention in drbd_worker Philipp Reisner
2014-09-11 12:29 ` [PATCH 9/9] drbd: Add missing newline in resync progress display in /proc/drbd Philipp Reisner
2014-09-11 15:12 ` [PATCH 0/9] DRBD updates for 3.18 Jens Axboe

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=1410438553-30440-1-git-send-email-philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=axboe@kernel.dk \
    --cc=drbd-dev@lists.linbit.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®