From: Jens Axboe <jens.axboe@oracle.com>
To: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
Cc: john smith <whalajam@yahoo.com>, fio@vger.kernel.org
Subject: Re: io scheduler merges control
Date: Mon, 11 Jan 2010 14:54:55 +0100 [thread overview]
Message-ID: <20100111135455.GN4489@kernel.dk> (raw)
In-Reply-To: <1262709179.10727.36.camel@cail>
On Tue, Jan 05 2010, Alan D. Brunelle wrote:
> On Mon, 2010-01-04 at 17:53 -0800, john smith wrote:
> > Alan,
> >
> > I've tried 'echo "1"> /sys/block/<dsf>/queue/nomerges' but
> > fio/sequential-reads merges still occur and apparently they are only
> > the simple ones that can't be disabled.
> >
> > 1) What can I change in the kernel to disable ALL the merges
> > (including the simple ones)?
> > (I tried setting iosched_cfq.ops.elevator_merge_fn,
> > elevator_merged_fn, elevator_merge_req_fn, elevator_allow_merge_fn = 0
> > but still fio reported merges)
>
> Unfortunately, the "simple" ones were left in precisely because they
> were (a) easy to do, and (b) were expected to happen often enough to
> keep them in. Jens may be able to comment further.
Right, they are both cheap and easy so they were kept. The goal with the
nomerges switch was to save CPU, so it'll still do cheap merges. I don't
think there's a use for disabling merges completely outside of device
testing and benchmarking, it's not a real world problem. That said, I do
occasionally hack that up as well for testing purposes. Perhaps we could
tweak nomerges to accept a '2' value as well, indicating that we don't
want any merges at all.
--
Jens Axboe
next prev parent reply other threads:[~2010-01-11 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 19:12 io scheduler merges control john smith
2010-01-04 14:34 ` Alan D. Brunelle
2010-01-05 1:53 ` john smith
2010-01-05 16:32 ` Alan D. Brunelle
2010-01-11 13:54 ` Jens Axboe [this message]
2010-01-14 18:37 ` john smith
2010-01-20 16:18 ` Alan D. Brunelle
2010-01-20 23:57 ` john smith
2010-01-11 6:15 ` Gurudas Pai
2010-01-11 13:52 ` Jens Axboe
2010-01-04 14:52 ` Chris Worley
2010-01-05 0:27 ` john smith
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=20100111135455.GN4489@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Alan.Brunelle@hp.com \
--cc=fio@vger.kernel.org \
--cc=whalajam@yahoo.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 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.