From: Jens Axboe <axboe@kernel.dk>
To: Philipp Reisner <philipp.reisner@linbit.com>,
linux-kernel@vger.kernel.org
Cc: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH 0/9] DRBD updates for 3.18
Date: Thu, 11 Sep 2014 09:12:10 -0600 [thread overview]
Message-ID: <5411BBCA.5070905@kernel.dk> (raw)
In-Reply-To: <1410438553-30440-1-git-send-email-philipp.reisner@linbit.com>
On 2014-09-11 06:29, Philipp Reisner wrote:
> 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.
Applied, thanks Philipp.
--
Jens Axboe
prev parent reply other threads:[~2014-09-11 15:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 12:29 [Drbd-dev] [PATCH 0/9] DRBD updates for 3.18 Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 1/9] drbd: Use better variable names Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 2/9] drbd: Use consistent names for all the bi_end_io callbacks Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 3/9] drbd: Remove superfluous newline from "resync_extents" debugfs entry Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 4/9] drbd: Avoid inconsistent locking warning Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 5/9] drbd: Get rid of the __no_warn and __cond_lock macros Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 6/9] drbd: Get rid of the WORK_PENDING macro Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 7/9] drbd: Improve asender performance Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 8/9] drbd: reduce lock contention in drbd_worker Philipp Reisner
2014-09-11 12:29 ` [Drbd-dev] [PATCH 9/9] drbd: Add missing newline in resync progress display in /proc/drbd Philipp Reisner
2014-09-11 15:12 ` Jens Axboe [this message]
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=5411BBCA.5070905@kernel.dk \
--to=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.com \
/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