public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Manish Regmi <regmi.manish@gmail.com>
Cc: Erik Mouw <mouw@nl.linux.org>,
	kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Linux disk performance.
Date: Tue, 19 Dec 2006 17:38:15 +1100	[thread overview]
Message-ID: <458788D7.2070107@yahoo.com.au> (raw)
In-Reply-To: <652016d30612182222h7fde4ea5jbc0927c8ebeae76a@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Manish Regmi wrote:

> Nick Piggin:
> 
>> but
>> they look like they might be a (HZ quantised) delay coming from
>> block layer plugging.
> 
> 
> Sorry i didn´t understand what you mean.

When you submit a request to an empty block device queue, it can
get "plugged" for a number of timer ticks before any IO is actually
started. This is done for efficiency reasons and is independent of
the IO scheduler used.

Use the noop IO scheduler, as well as the attached patch, and let's
see what your numbers look like.

Thanks,
Nick

-- 
SUSE Labs, Novell Inc.

[-- Attachment #2: block-no-plug.patch --]
[-- Type: text/plain, Size: 516 bytes --]

Index: linux-2.6/block/ll_rw_blk.c
===================================================================
--- linux-2.6.orig/block/ll_rw_blk.c	2006-12-19 17:35:00.000000000 +1100
+++ linux-2.6/block/ll_rw_blk.c	2006-12-19 17:35:53.000000000 +1100
@@ -226,6 +226,8 @@ void blk_queue_make_request(request_queu
 	q->unplug_delay = (3 * HZ) / 1000;	/* 3 milliseconds */
 	if (q->unplug_delay == 0)
 		q->unplug_delay = 1;
+	q->unplug_delay = 0;
+	q->unplug_thresh = 0;
 
 	INIT_WORK(&q->unplug_work, blk_unplug_work, q);
 

  reply	other threads:[~2006-12-19  6:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  4:07 Linux disk performance Manish Regmi
2006-12-18  8:35 ` Arjan van de Ven
2006-12-18 12:39   ` Manish Regmi
2006-12-18 12:54     ` Nick Piggin
2006-12-18 13:07     ` Erik Mouw
2006-12-19  6:22       ` Manish Regmi
2006-12-19  6:38         ` Nick Piggin [this message]
2006-12-19 12:18           ` Arjan van de Ven
2006-12-20 11:17           ` Manish Regmi
2006-12-22  0:14             ` Bhanu Kalyan Chetlapalli
2006-12-22  5:30               ` Manish Regmi
2006-12-22  5:39                 ` Bhanu Kalyan Chetlapalli
2006-12-22  5:56                   ` Manish Regmi
2006-12-20 22:29     ` Bill Davidsen
2006-12-21  6:03       ` Manish Regmi
2006-12-21  7:15         ` Daniel Cheng
2006-12-21 13:22         ` Erik Mouw
2006-12-22  5:39           ` Manish Regmi
2006-12-27 15:50       ` Phillip Susi
2007-01-01  1:59         ` Bill Davidsen

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=458788D7.2070107@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mouw@nl.linux.org \
    --cc=regmi.manish@gmail.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