| To: | kuznet@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: tx_timeout and timer serialisation |
| From: | Andrew Morton <andrewm@xxxxxxxxxx> |
| Date: | Thu, 25 May 2000 23:22:38 +0000 |
| Cc: | netdev@xxxxxxxxxxx |
| References: | <3923F8CD.AECBDA6D@xxxxxxxxxx> from "Andrew Morton" at May 19, 0 00:06:05 am <200005251831.WAA21251@xxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
kuznet@xxxxxxxxxxxxx wrote:
>
> ...
> > It can delete the
> > timer and kfree it, or reuse its memory for something else,
> > or turn it into a semantically different timer **
>
> Yes, and in this case you cannot use del_timer_sync() and
> have to use generic reference counting scheme.
To use refcounting we need a new sort of timer, so the timer core can
manage their storage. So instead of having:
struct some_struct
{
...
struct timer_list timer;
...
}
we have:
struct some_struct
{
...
struct new_timer *timer;
...
}
--
-akpm-
|
| Previous by Date: | Re: tx_timeout and timer serialisation, 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] |