From: Andrew Morton <akpm@osdl.org>
To: kenneth.w.chen@intel.com, linux-kernel@vger.kernel.org
Subject: Re: per-cpu blk_plug_list
Date: Mon, 1 Mar 2004 14:31:39 -0800 [thread overview]
Message-ID: <20040301143139.474fe56e.akpm@osdl.org> (raw)
In-Reply-To: <20040301141728.71e49546.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
>
> @@ -1251,6 +1251,9 @@ void blk_run_queues(void)
> {
> LIST_HEAD(local_plug_list);
>
> + if (list_empty(&blk_plug_list))
> + return;
> +
hmm, no, that won't help. There will always be at least one plugged disk.
Perhaps what we need here is a per-task container of "queues which I have
plugged". Or, more accurately, "queues which need to be unplugged so that
I can complete". It'll get tricky because in some situations a task can
need unplugging of a queue which it did not plug, and even a queue to which
it did not submit any I/O.
You should try just nuking the whole plugging scheme, btw. Stick a bunch
of `return' statements at the top of all the plugging functions. I bet
that would run nicely...
next prev parent reply other threads:[~2004-03-01 22:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 21:18 Chen, Kenneth W
2004-03-01 22:06 ` Jens Axboe
2004-03-01 22:17 ` Andrew Morton
2004-03-01 22:31 ` Andrew Morton [this message]
[not found] ` <B05667366EE6204181EABE9C1B1C0EB501F2AB4C@scsmsx401.sc.intel.com.suse.lists.linux.kernel>
2004-03-01 22:36 ` Andi Kleen
2004-03-01 22:39 ` per-cpu blk_plug_list II Andi Kleen
2004-03-03 3:44 ` per-cpu blk_plug_list Jesse Barnes
2004-03-03 3:55 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-03-03 4:20 Chen, Kenneth W
2004-03-03 5:13 ` Andrew Morton
2004-03-03 9:45 ` Miquel van Smoorenburg
2004-03-03 9:54 ` Andrew Morton
2004-03-03 16:24 ` Miquel van Smoorenburg
2004-03-03 22:37 ` Miquel van Smoorenburg
2004-03-01 22:28 Chen, Kenneth W
2004-03-01 22:14 Chen, Kenneth W
[not found] <cistron.B05667366EE6204181EABE9C1B1C0EB50211E5C8@scsmsx401.sc.intel.com>
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=20040301143139.474fe56e.akpm@osdl.org \
--to=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®