linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matias Bjørling" <m@bjorling.me>
To: axboe@kernel.dk, sbradshaw@micron.com
Cc: linux-kernel@vger.kernel.org, "Matias Bjørling" <m@bjorling.me>
Subject: [PATCH] block: small performance optimization
Date: Fri,  9 May 2014 11:17:40 +0200	[thread overview]
Message-ID: <1399627061-5960-1-git-send-email-m@bjorling.me> (raw)

Hi Jens,

The IO accounting stats contribute significant overhead on high IO/multi-node
workloads. By moving the in_flight IO tracking to per-cpu counters, we can
elevate some of the cache coherence overhead, at the cost of setup/teardown
and percpu counters structure within the hd_struct structure.

Sam Bradshaw reported an IOPS increase of 20% on his fio workloads.

Thanks,
Matias

Matias Bjørling (1):
  blk: per-cpu counters for in-flight IO accounting

 block/partition-generic.c |  4 ++--
 include/linux/genhd.h     | 25 ++++++++++++++++++-------
 2 files changed, 20 insertions(+), 9 deletions(-)

-- 
1.9.1


             reply	other threads:[~2014-05-09  9:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09  9:17 Matias Bjørling [this message]
2014-05-09  9:17 ` [PATCH] block: per-cpu counters for in-flight IO accounting Matias Bjørling
2014-05-09 14:12   ` Jens Axboe
2014-05-09 16:41     ` Jens Axboe
2014-05-30 12:11       ` Shaohua Li
2014-05-30 13:49         ` Jens Axboe
2014-06-04 10:39           ` Shaohua Li
2014-06-04 11:29             ` Matias Bjørling
2014-06-04 20:08               ` Jens Axboe
2014-06-05  2:09                 ` Shaohua Li
2014-06-05  2:16                   ` Jens Axboe
2014-06-05  2:33                     ` Shaohua Li
2014-06-05  2:42                       ` Jens Axboe
2014-06-04 14:29             ` 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=1399627061-5960-1-git-send-email-m@bjorling.me \
    --to=m@bjorling.me \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbradshaw@micron.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;
as well as URLs for NNTP newsgroup(s).