From: Johannes Erdfelt <jerdfelt@valinux.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Oleg Drokin <green@ixcelerator.com>, linux-kernel@vger.kernel.org
Subject: Re: hardcoded HZ in hub.c
Date: Tue, 21 Nov 2000 09:56:26 -0800 [thread overview]
Message-ID: <20001121095626.F3431@valinux.com> (raw)
In-Reply-To: <20001120121746.F895@valinux.com> <20001117125441.A28208@iXcelerator.com> <20001120121746.F895@valinux.com> <1891.974801599@redhat.com>
In-Reply-To: <1891.974801599@redhat.com>; from dwmw2@infradead.org on Tue, Nov 21, 2000 at 10:13:19AM +0000
On Tue, Nov 21, 2000, David Woodhouse <dwmw2@infradead.org> wrote:
>
> jerdfelt@valinux.com said:
> > We applied a slightly different patch which is would not remove the
> > pages out from under the thread, using semaphores instead.
>
> > This patch isn't needed anymore. Thanks anyway.
>
> Actually, the best fix is probably to get rid of the thread entirely and use
> schedule_task to run usb_hub_events() instead.
That that possible? usb_hub_events can block for a long time. That is why
the kernel thread was needed. I'm not familiar with schedule_task enough
to know if it can be used.
JE
-
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-21 18:27 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 [this message]
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
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=20001121095626.F3431@valinux.com \
--to=jerdfelt@valinux.com \
--cc=dwmw2@infradead.org \
--cc=green@ixcelerator.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.