20 captures
08 Jun 2013 - 28 Nov 2025
May JUN Jul
08
2012 2013 2014
success
fail

About this capture

COLLECTED BY

Organization: Alexa Crawls

Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period.

Collection: Alexa Crawls

Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period.
TIMESTAMPS

The Wayback Machine - http://web.archive.org/web/20130608123735/http://lwn.net:80/Articles/549707/
 
LWN.net Logo

Log in now

Create an account

Subscribe to LWN

Little things that matter in language design

LWN.net Weekly Edition for June 6, 2013

Power-aware scheduling meets a line in the sand

Trusting upstream

LWN.net Weekly Edition for May 31, 2013

(Nearly) full tickless operation in 3.10

(Nearly) full tickless operation in 3.10

Posted May 8, 2013 20:23 UTC (Wed) by intgr (subscriber, #39733)
In reply to: (Nearly) full tickless operation in 3.10 by corbet
Parent article: (Nearly) full tickless operation in 3.10

Sorry, it's much more likely that I am missing something.

AFAICT the scheduler doesn't switch tasks at every timer tick, even when there is contention for a CPU -- it has its own concept of timeslice length that changes with load. So why does a contended CPU need to run the timer tick if it's not going to switch tasks?

And grandparent wrote something that seemed to match that line of thinking:

> After a little RTFC, I found that a HR-timer was used to calculate the next preemption point. I.e. instead of preempting on 100 Hz clock, it preempts exactly when the timeslot of the current process ends.


(Log in to post comments)

(Nearly) full tickless operation in 3.10

Posted May 9, 2013 2:16 UTC (Thu) by nevets (subscriber, #11875) [Link]

It's confusing because there's two things at play here. There's the hrtick and the scheduler_tick.

The hrtick is used to denote exact time slices for the CFS scheduler to create more fairness. It really doesn't do much more than that. But this does not replace the scheduler_tick, which does among other things, keeps track of the SCHED_RR time slices, manages load balancing, and updates task timings.

But I'm sure in the future the hrtick may be used more to get rid of the periodic tick.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds