linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: Fix up riscom8 driver to use work queues instead of task queueing.
Date: Mon, 18 Aug 2003 13:32:26 -0700	[thread overview]
Message-ID: <20030818133226.66986354.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0308181234500.5929-100000@home.osdl.org>

Linus Torvalds <torvalds@osdl.org> wrote:
>
> 
> On Mon, 18 Aug 2003, Jeff Garzik wrote:
> > 
> > There was talk in another thread about fixing up workqueue to create
> > a new kernel thread, if one isn't available within five seconds.
> 
> That's probably reasonable. Together with some upper limit to active
> threads, along with timeouting old queues when idle it would be fairly
> flexible. It's how basically all servers end up working, after all. It 
> shouldn't be that hard to do.
> 

Note that pdflush is already doing this.  It doesn't seem to work very well
though:

a) new threads seem to start up too late

b) they probably don't hang around for long enough

c) now that pdflush avoids blocking on queues it's all rather overkill
   anyway.

pdflush could kinda-sorta be converted to use workqueues, but it doesn't
want a thread per cpu.


  reply	other threads:[~2003-08-18 20:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200308181806.h7II6K6D014918@hera.kernel.org>
2003-08-18 18:09 ` Fix up riscom8 driver to use work queues instead of task queueing Jeff Garzik
2003-08-18 18:21   ` Linus Torvalds
2003-08-18 18:28     ` Russell King
2003-08-18 18:47       ` Linus Torvalds
2003-08-18 18:59         ` Russell King
2003-08-18 19:10           ` Linus Torvalds
2003-08-18 18:44     ` Jeff Garzik
2003-08-18 19:12       ` Linus Torvalds
2003-08-18 19:25         ` Jeff Garzik
2003-08-18 19:36           ` Linus Torvalds
2003-08-18 20:32             ` Andrew Morton [this message]
2003-08-18 21:24               ` Jeff Garzik

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=20030818133226.66986354.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).