mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Corrado Zoccolo <czoccolo@gmail.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	aaronc@gelato.unsw.edu.au
Subject: Re: [RFC, PATCH] cfq-iosched: remove redundant queuing detection code
Date: Tue, 10 Nov 2009 10:20:18 -0500	[thread overview]
Message-ID: <x49ocna5rv1.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20091110151431.GI8742@kernel.dk> (Jens Axboe's message of "Tue, 10 Nov 2009 16:14:31 +0100")

Jens Axboe <jens.axboe@oracle.com> writes:

> On Tue, Nov 10 2009, Corrado Zoccolo wrote:
>> The core block layer already has code to detect presence of command
>> queuing devices. We convert cfq to use that instead of re-doing the
>> computation.
>
> There's is the major difference that the CFQ variant is dynamic and the
> block layer one is not. This change came from Aaron some time ago IIRC,
> see commit 45333d5. It's a bit of a chicken and egg problem.

Really?  blk_dequeue_request sure looks like it updates things
dynamically, but only one way (not queueing -> queueing).  Would it make
sense to just put CFQ's logic into the block layer so that everyone uses
the same implementation?  It makes little sense to have two notions of
whether or not queueing is supported for a device.

Cheers,
Jeff

  reply	other threads:[~2009-11-10 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 13:54 Corrado Zoccolo
2009-11-10 15:03 ` Jeff Moyer
2009-11-10 15:14 ` Jens Axboe
2009-11-10 15:20   ` Jeff Moyer [this message]
2009-11-10 15:27     ` Jens Axboe
2009-11-10 15:41       ` Jeff Moyer
2009-11-10 15:48         ` Jens Axboe
2009-11-10 15:55           ` Jeff Moyer
2009-11-10 17:56   ` Corrado Zoccolo
2009-11-12 12:16     ` Jens Axboe
2009-11-12 13:14       ` Corrado Zoccolo
2009-11-12 13:16         ` 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=x49ocna5rv1.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=aaronc@gelato.unsw.edu.au \
    --cc=czoccolo@gmail.com \
    --cc=jens.axboe@oracle.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

all inboxes | Powered by JetHome®