From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test13-pre1 lockup: run_task_queue or tty_io are wrong
Date: 17 Dec 2000 12:23:33 -0800 [thread overview]
Message-ID: <91j7c5$pl1$1@penguin.transmeta.com> (raw)
In-Reply-To: <20001217192351.A18244@pcep-jamie.cern.ch> <Pine.LNX.4.10.10012171200310.25447-100000@penguin.transmeta.com> <20001217140530.A14173@vger.timpanogas.org>
In article <20001217140530.A14173@vger.timpanogas.org>,
Jeff V. Merkey <jmerkey@vger.timpanogas.org> wrote:
>
>Try thinking about the work to do model (since task queues are so similiar)
>Having to "kick" these things should be automatic in the kernel. I could
>do a lot of cool stuff with this in there, manos aside.....
No, the "kicking" should _not_ be automatic.
Th ewhol epoint of a lot of the task queues is that they are manual. The
main use for them (apart from the tty layer, which could easily use
something else) is the disk starter - where we want to delay the
submission of requests to the disk until we've aggregated as many as
possible. Which means that the "tq_disk" queue must absolutely not be
kicked automatically.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-17 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 2:49 2.4.0-test13-pre1 lockup: run_task_queue or tty_io are wrong Petr Vandrovec
2000-12-17 3:09 ` Linus Torvalds
2000-12-17 3:49 ` Petr Vandrovec
2000-12-17 7:25 ` Andrew Morton
2000-12-17 18:23 ` Jamie Lokier
2000-12-17 20:02 ` Linus Torvalds
2000-12-17 21:05 ` Jeff V. Merkey
2000-12-17 20:23 ` Linus Torvalds [this message]
2000-12-18 20:51 ` Jamie Lokier
2000-12-18 23:58 ` Linus Torvalds
2000-12-19 1:32 ` Jamie Lokier
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='91j7c5$pl1$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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