From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: Johannes Erdfelt <johannes@erdfelt.com>,
Oleg Drokin <green@ixcelerator.com>,
linux-kernel@vger.kernel.org
Subject: Re: hardcoded HZ in hub.c
Date: Wed, 22 Nov 2000 11:26:00 +0000 [thread overview]
Message-ID: <9719.974892360@redhat.com> (raw)
In-Reply-To: <3A1BAC59.B0F124AF@uow.edu.au>
In-Reply-To: <3A1BAC59.B0F124AF@uow.edu.au> <20001121142616.L7764@sventech.com>, <20001121142616.L7764@sventech.com> <20001121095626.F3431@valinux.com> <Pine.LNX.4.30.0011211912490.22252-100000@imladris.demon.co.uk> <4627.974890115@redhat.com>
andrewm@uow.edu.au said:
> Nothing which sleeps for very long - mainly serial drivers which
> queue a call to tty_hangup(), which immediately queues _another_
> tq_scheduler call to do_tty_hangup (Why? Heaven knows).
Not so much worried about that. More about how sensitive they would be to
something _else_ causing the eventd thread to sleep for 'multiple seconds'
before getting round to doing what they asked.
I really don't want to have to start using multiple eventd threads before
2.5, if at all. So I don't want to add the USB hub stuff unless the other
queued tasks will be happy with that.
--
dwmw2
-
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-11-22 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 9:54 hardcoded HZ in hub.c Oleg Drokin
2000-11-20 20:17 ` Johannes Erdfelt
2000-11-21 10:13 ` David Woodhouse
2000-11-21 17:56 ` Johannes Erdfelt
2000-11-21 19:13 ` David Woodhouse
2000-11-21 19:26 ` Johannes Erdfelt
2000-11-22 10:48 ` David Woodhouse
2000-11-22 11:22 ` Andrew Morton
2000-11-22 11:26 ` David Woodhouse [this message]
2000-11-22 11:34 ` Andrew Morton
2000-11-22 11:47 ` David Woodhouse
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=9719.974892360@redhat.com \
--to=dwmw2@infradead.org \
--cc=andrewm@uow.edu.au \
--cc=green@ixcelerator.com \
--cc=johannes@erdfelt.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