Hi,
On Thu, 9 Nov 2006, Thomas Gleixner wrote:
> From: Thomas Gleixner <[email protected]>
>
> Reintroduce ktimers feature "optimized away" by the ktimers review process:
> multiple hrtimer states to enable the running of hrtimers without holding the
> cpu-base-lock.
They were "optimized away" for a reason...
> (The "optimized" rbtree hack carried only 2 states worth of information and we
> need 4 for high resolution timers and dynamic ticks.)
If you need further flags for dynticks, then to do it conditionally, but
keep this as is (at least for now), keep it small for the simple stuff.
As others have noted your usage is confusing, something like this hard to
maintain - every time a flag is added/changed, almost every user has to
checked to insure the state machine stays correct. Keep the basic states
separate and if it the flag field should be needed for other reason, it
should be easy enough to convert. This is not needed for an initial merge.
(Same goes for the next patch.)
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]
