From: Andrew Morton <andrewm@uow.edu.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "David S. Miller" <davem@redhat.com>,
Russell King <rmk@arm.linux.org.uk>,
Ben LaHaise <bcrl@redhat.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1
Date: Tue, 12 Jun 2001 00:21:36 +1000 [thread overview]
Message-ID: <3B24D3F0.F2B6DA76@uow.edu.au> (raw)
In-Reply-To: <3B23A4BB.7B4567A3@mandrakesoft.com> <20010610093838.A13074@flint.arm.linux.org.uk> <Pine.LNX.4.33.0106101201490.9384-100000@toomuch.toronto.redhat.com> <20010610173419.B13164@flint.arm.linux.org.uk> <15140.5762.589629.252904@pizda.ninka.net> <3B24C185.824EBBE0@uow.edu.au> <15140.51018.942446.320621@pizda.ninka.net> <3B24CC80.D880510@mandrakesoft.com>
Jeff Garzik wrote:
>
> "David S. Miller" wrote:
> >
> > Andrew Morton writes:
> > > It'd need to be callable from interrupt context - otherwise
> > > each device/driver which has link status change interrupts
> > > will need to implement some form of interrupt->process context
> > > trick.
> >
> > Well, we could make the netif_carrier_*() implementation do the
> > "interrupt->process context" trick.
> >
> > Jamal can feel free to post what he has.
>
> If we have any problems with context we can always use schedule_task()
Yep. With dev_hold() and dev_put() to avoid module removal
races. One would also have to be sure that the right things
happen if the interface is downed between the interrupt and
execution of the schedule_task() callback.
next prev parent reply other threads:[~2001-06-11 14:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 17:45 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1 Glenn C. Hofmann
2001-06-10 1:35 ` Andrew Morton
2001-06-10 4:56 ` Glenn C. Hofmann
2001-06-10 5:08 ` Glenn C. Hofmann
2001-06-10 5:54 ` Ben LaHaise
2001-06-10 8:38 ` Russell King
2001-06-10 9:39 ` arjan
2001-06-10 16:06 ` Ben LaHaise
2001-06-10 16:34 ` Russell King
2001-06-10 16:47 ` Jeff Garzik
2001-06-10 22:23 ` Ben LaHaise
2001-06-11 0:53 ` David S. Miller
2001-06-11 13:03 ` Andrew Morton
2001-06-11 13:27 ` David S. Miller
2001-06-11 13:49 ` Jeff Garzik
2001-06-11 14:21 ` Andrew Morton [this message]
2001-06-11 16:05 ` Jeff Garzik
2001-06-11 3:17 ` Glenn C. Hofmann
2001-06-11 3:25 ` Jeff Garzik
2001-06-12 3:17 ` Glenn C. Hofmann
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=3B24D3F0.F2B6DA76@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=bcrl@redhat.com \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rmk@arm.linux.org.uk \
/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.