public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] use cheaper elv_queue_empty when unplug a device
Date: Tue, 29 Mar 2005 19:21:48 +1000	[thread overview]
Message-ID: <42491E2C.2070702@yahoo.com.au> (raw)
In-Reply-To: <42491DBE.6020303@yahoo.com.au>

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

Nick Piggin wrote:

> I haven't used a big disk array (or tried any simulation), but I'll
> attach the patch if you're looking into that area.
> 

Oh, and this one removes a memory barrier. I think we (Jens and I)
agreed this is valid. Whether or not you'll notice a difference is
another story ;)


[-- Attachment #2: blk-no-mb.patch --]
[-- Type: text/plain, Size: 1192 bytes --]



This memory barrier is not needed because the waitqueue will only get
waiters on it in the following situations:

rq->count has exceeded the threshold - however all manipulations of ->count
are performed under the runqueue lock, and so we will correctly pick up any
waiter.

Memory allocation for the request fails. In this case, there is no additional
help provided by the memory barrier. We are guaranteed to eventually wake
up waiters because the request allocation mempool guarantees that if the mem
allocation for a request fails, there must be some requests in flight. They
will wake up waiters when they are retired.



---

 linux-2.6-npiggin/drivers/block/ll_rw_blk.c |    1 -
 1 files changed, 1 deletion(-)

diff -puN drivers/block/ll_rw_blk.c~blk-no-mb drivers/block/ll_rw_blk.c
--- linux-2.6/drivers/block/ll_rw_blk.c~blk-no-mb	2005-03-29 18:58:19.000000000 +1000
+++ linux-2.6-npiggin/drivers/block/ll_rw_blk.c	2005-03-29 19:20:10.000000000 +1000
@@ -1828,7 +1828,6 @@ static void __freed_request(request_queu
 		clear_queue_congested(q, rw);
 
 	if (rl->count[rw] + 1 <= q->nr_requests) {
-		smp_mb();
 		if (waitqueue_active(&rl->wait[rw]))
 			wake_up(&rl->wait[rw]);
 

_

  reply	other threads:[~2005-03-29  9:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29  2:53 [patch] use cheaper elv_queue_empty when unplug a device Chen, Kenneth W
2005-03-29  8:06 ` Jens Axboe
2005-03-29  9:19   ` Nick Piggin
2005-03-29  9:21     ` Nick Piggin [this message]
2005-03-29  9:28     ` Jens Axboe
2005-03-29  9:50       ` Nick Piggin
2005-03-29 10:06       ` Nick Piggin
2005-03-30  0:57         ` Nick Piggin
2005-03-30  8:11           ` Jens Axboe
2005-04-08  9:45           ` Jens Axboe
2005-04-08  9:55             ` Nick Piggin
2005-04-08 10:02               ` Jens Axboe
2005-04-08 10:22                 ` Nick Piggin
2005-03-29 10:10     ` Arjan van de Ven
2005-03-29 10:19       ` Jens Axboe
2005-03-29 10:23       ` Nick Piggin
2005-03-29 13:15     ` Jens Axboe
2005-03-30  0:07       ` Nick Piggin
2005-03-29 19:02     ` Chen, Kenneth W

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=42491E2C.2070702@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=axboe@suse.de \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-kernel@vger.kernel.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