From: Mel Gorman <mgorman@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Linux-FSDevel <linux-fsdevel@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>, Johannes Weiner <hannes@cmpxchg.org>,
Jens Axboe <axboe@kernel.dk>, Mel Gorman <mgorman@suse.de>
Subject: [PATCH 0/4] Improve sequential read throughput
Date: Wed, 18 Jun 2014 09:23:23 +0100 [thread overview]
Message-ID: <1403079807-24690-1-git-send-email-mgorman@suse.de> (raw)
IO performance since 3.0 has been a mixed bag. In many respects we are
better and in some we are worse and one of those places is sequential read
performance, particularly for higher numbers of threads. This is visible
in a number of benchmarks but tiobench has been the one I looked at the
closest despite its age.
3.16.0-rc1 3.16.0-rc1 3.0.0
vanilla patch-series vanilla
Mean SeqRead-MB/sec-1 121.88 ( 0.00%) 133.84 ( 9.81%) 134.59 ( 10.42%)
Mean SeqRead-MB/sec-2 101.99 ( 0.00%) 115.01 ( 12.77%) 122.59 ( 20.20%)
Mean SeqRead-MB/sec-4 97.42 ( 0.00%) 108.40 ( 11.27%) 114.78 ( 17.82%)
Mean SeqRead-MB/sec-8 83.39 ( 0.00%) 97.50 ( 16.92%) 100.14 ( 20.09%)
Mean SeqRead-MB/sec-16 68.90 ( 0.00%) 82.14 ( 19.22%) 81.64 ( 18.50%)
The impact on the other operations is negligible. Note that 3.0-vanilla is
still far better but bringing the patch series further in line would involve
increasing the CFQ target latency higher and there should be better options.
This series is a major improvement on 3.16-rc1-vanilla at least so worth
sending out to a larger audience for comment.
block/cfq-iosched.c | 2 +-
include/linux/mmzone.h | 9 +++
include/linux/writeback.h | 1 +
include/trace/events/pagemap.h | 16 ++--
mm/internal.h | 1 +
mm/mm_init.c | 5 +-
mm/page-writeback.c | 15 ++--
mm/page_alloc.c | 176 ++++++++++++++++++++++++++---------------
mm/swap.c | 4 +-
9 files changed, 144 insertions(+), 85 deletions(-)
--
1.8.4.5
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-06-18 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 8:23 Mel Gorman [this message]
2014-06-18 8:23 ` [PATCH 1/4] cfq: Increase default value of target_latency Mel Gorman
2014-06-19 18:38 ` Jeff Moyer
2014-06-19 21:42 ` Dave Chinner
2014-06-20 11:30 ` Mel Gorman
2014-06-21 0:39 ` Dave Chinner
2014-06-20 11:28 ` Mel Gorman
2014-06-18 8:23 ` [PATCH 2/4] mm: pagemap: Avoid unnecessary overhead when tracepoints are deactivated Mel Gorman
2014-06-18 8:23 ` [PATCH 3/4] mm: page_alloc: Reset fair zone allocation policy when batch counts are expired Mel Gorman
2014-06-18 20:01 ` Johannes Weiner
2014-06-18 21:57 ` Mel Gorman
2014-06-19 18:18 ` Johannes Weiner
2014-06-18 8:23 ` [PATCH 4/4] mm: page_alloc: Reduce cost of dirty zone balancing Mel Gorman
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=1403079807-24690-1-git-send-email-mgorman@suse.de \
--to=mgorman@suse.de \
--cc=axboe@kernel.dk \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).