Russell King <[email protected]> wrote:
> I assume you wanted to delete "data" ?
Yes.
> Your premise is two timer_lists which use one common handler.
>
> struct foo {
> struct timer_list timer1;
> strucr timer_list timer2;
> };
That's not what I was thinking of. I was thinking of something much simpler:
struct foo {
struct timer_list timer;
};
...
struct foo *a = kmalloc(sizeof(struct foo), GFP_KERNEL);
a->timer.fn = do_foo_timer;
...
struct foo *b = kmalloc(sizeof(struct foo), GFP_KERNEL);
b->timer.fn = do_foo_timer;
...
struct foo *c = kmalloc(sizeof(struct foo), GFP_KERNEL);
c->timer.fn = do_foo_timer;
...
struct foo *d = kmalloc(sizeof(struct foo), GFP_KERNEL);
d->timer.fn = do_foo_timer;
...
You've now got four copies of struct timer_list, but only one handler.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [RFC] timers, pointers to functions and type safety
- [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
- Re: [RFC] timers, pointers to functions and type safety
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]