| To: | kuznet@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: tx_timeout and timer serialisation |
| From: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx> |
| Date: | Tue, 30 May 2000 14:28:41 -0400 |
| Cc: | Rusty Russell <rusty@xxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| Organization: | MandrakeSoft |
| References: | <200005301729.VAA12781@xxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
kuznet@xxxxxxxxxxxxx wrote:
> But both ways are still wrong. We still need macro telling,
> when a self-destructable timer is running even if we need not
> any synchronization. So that timer_exit() is required in any case.
It seems like any solution requiring timer_exit() will always be racy,
because of the [very small] window between timer_exit() code finishing,
and the timer function code being disposeable...
Jeff
--
Jeff Garzik | Liberty is always dangerous, but
Building 1024 | it is the safest thing we have.
MandrakeSoft, Inc. | -- Harry Emerson Fosdick
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [timers] net/sched/*, Andrew Morton |
|---|---|
| Next by Date: | Re: tx_timeout and timer serialisation, kuznet |
| Previous by Thread: | Re: tx_timeout and timer serialisation, kuznet |
| Next by Thread: | Re: tx_timeout and timer serialisation, kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |