Hi,
On Mon, 17 Oct 2005, Tim Bird wrote:
> Maybe for a more experienced kernel person such as
> yourself, this distinction make sense. But
> "process timer" and "kernel timer" don't carry much
> semantic value for me. They seem to convey an
> arbitrary expectation of usage patterns. Maybe
> they match the current usage patterns in the kernel,
> but I'd prefer naming based on functionality or
> behaviour of the API.
Let's say you want to implement a watchdog timer for a driver, which runs
about every second to do something. Now if you have the choice between
"timer API" vs. "timeout API" and "kernel timer" vs. "process timer", what
would you choose based on the name?
bye, Roman
-
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/
[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]
