From: Nick Piggin <piggin@cyberone.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: queue reference counting
Date: Thu, 07 Aug 2003 19:26:34 +1000 [thread overview]
Message-ID: <3F321B4A.6060403@cyberone.com.au> (raw)
In-Reply-To: <20030807092237.GB858@suse.de>
Jens Axboe wrote:
>On Thu, Aug 07 2003, Nick Piggin wrote:
>
>>
>>Jens Axboe wrote:
>>
>>
>>>On Thu, Aug 07 2003, Pavel Machek wrote:
>>>
>>>
>>>>Hi!
>>>>
>>>>
>>>>
>>>>>I ported `subj` to 2.6.0-test2. I do not yet have idea if it works,
>>>>>but it compiles ;-).
>>>>>
>>>>>
>>>>It compiles, it event boots, but it does not seem to have much effect
>>>>:-(.
>>>>
>>>>
>>>Now that the queue reference counting is in the current bk tree, we are
>>>that much closer to real modular io schedulers. I'll post the cfq with
>>>priorities for that.
>>>
>>>
>>OK, the QUEUE_FLAG_DEAD. I assume that will be set in blk_cleanup_queue?
>>Then all remaining requests are flushed out of the queue?
>>
>>This requires that a driver must be able to continue to process requests
>>during the call to blk_cleanup_queue, and that blk_cleanup_queue might
>>block, right? Is this acceptable, or should there be an earlier call to
>>set QUEUE_FLAG_DEAD and ensure queue is flushed?
>>
>
>The plan was to add blk_shutdown_queue() to do this. And then make sure
>AS checks the dead flag and doesn't hold back any requests.
>
Sounds sensible. Just ensuring I wasn't missing out on the fun.
next prev parent reply other threads:[~2003-08-07 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 23:28 Disk priority dependend on nice level Pavel Machek
2003-08-06 23:40 ` Pavel Machek
2003-08-07 8:02 ` Jens Axboe
2003-08-07 9:20 ` queue reference counting Nick Piggin
2003-08-07 9:22 ` Jens Axboe
2003-08-07 9:26 ` Nick Piggin [this message]
2003-08-07 10:04 ` Disk priority dependend on nice level Pavel Machek
2003-08-07 10:09 ` Jens Axboe
2003-08-07 5:57 ` Jens Axboe
2003-08-07 10:01 ` Pavel Machek
2003-08-07 10:09 ` 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=3F321B4A.6060403@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=axboe@suse.de \
--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