From: Andrew Morton <andrewm@uow.edu.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org,
Rik van Riel <riel@conectiva.com.br>,
netdev@oss.sgi.com
Subject: Re: PATCH: 8139too kernel thread
Date: Sat, 11 Nov 2000 11:48:56 +1100 [thread overview]
Message-ID: <3A0C9778.E982F55B@uow.edu.au> (raw)
In-Reply-To: <200011102129.QAA13369@havoc.gtf.org>
Jeff Garzik wrote:
>
> (note Linus, not for applying...)
>
> Here is a patch, against 2.4.0-test11-pre2, that I wanted to forward
> to the lists for comment.
>
> Many of the ethernet drivers have timer routines, which are
> called every three-five seconds or so. These timer routines
> typically do stuff related to media selection or checking, and call
> mdio_{read,write} to interact with the phy.
>
I think it's useful. More generally, I'd like to have
"process context timers" - the ability to call a function
from process context at a set time. Then a single kernel
thread could handle all things like this. Pretty simple to do.
BTW: can the OOM killer possibly kill a kernel thread?
If it does, yenta_socket_thread() will nuke the machine.
-
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-11 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 21:29 PATCH: 8139too kernel thread Jeff Garzik
2000-11-11 0:48 ` Andrew Morton [this message]
2000-11-16 17:59 ` Alan Cox
2000-11-16 18:05 ` Alexander Viro
2000-11-16 18:10 ` Linus Torvalds
2000-11-16 18:28 ` Jeff Garzik
2000-11-16 18:19 ` Alan Cox
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=3A0C9778.E982F55B@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=riel@conectiva.com.br \
/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.