[lkml]   [2008]   [Aug]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4/5] select: make select() use schedule_hrtimeout()

On Fri, 29 Aug 2008, Alan Cox wrote:
> Most of the timers we want to aggregate with are kernel originated and
> those also need accuracy fields (tcp retransmit is fairly precision at
> high speed while tcp keepalive is 'yeah whatever' sort of urgency.

Actually, I disagree.

They are _both_ of the exact same type: the precision depends on how long
the timeout is.

TCP retransmit timers are a perfect example. If the timeout is long (which
is quite common if you end up having multiple retransmits), you _really_
don't care about how precise it is.

And keepalives are 'yeah whatever' exactly because they are so long, not
because they are inherently uninteresting per se.

I suspect you could find some kernel-generated timer that doesn't fit that
pattern, but I can't really think of any.

> Agreed except that I'd assume real time tasks implied high accuracy,
> otherwise one assumes they'd have not have been real time - and probably
> putting those constants into sysfs somewhere.

And yes, I do agree that the heuristic could well involve other
characteristics of the process in question. And probably characteristics
of the machine itself (ie some general kind of "power mode" where timers
are simply not considered critical if you want to be in low-power mode).


 \ /
  Last update: 2008-08-29 20:49    [W:0.076 / U:0.084 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site