Balbir Singh wrote:
Peter Williams wrote:
You're over engineering and you're not solving the problem. You're
just moving it down a bit.
2. In a group based cap management system, schedule some tasks
(highest priority)
until their cap run out. In the subsequent rounds pick and choose
tasks that
did not get a chance to run earlier.
Solving this is indeed a interesting problem.
Once again, you're over engineering and probably making the problem
worse.
I like this term over-engineering. Lets focus on the solution for the most
common case and see what works out. I was pointing you to the possible
limitations of the approach, which is always a good thing to do in
engineering.
And I was pointing out that it's a fundamental limitation that can't be
avoided no matter which implementation route you follow.
Peter
--
Dr Peter Williams, Chief Scientist <[email protected]>
Aurema Pty Limited
Level 2, 130 Elizabeth St, Sydney, NSW 2000, Australia
Tel:+61 2 9698 2322 Fax:+61 2 9699 9174 http://www.aurema.com
-
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]