Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?)

From: Peter Jeremy (PeterJeremy_at_optushome.com.au)
Date: 10/31/05

  • Next message: Eric Hodel: "Re: MySQL Performance 6.0rc1"
    Date: Tue, 1 Nov 2005 05:00:37 +1100
    To: Poul-Henning Kamp <phk@phk.freebsd.dk>
    
    

    On Mon, 2005-Oct-31 11:26:38 +0100, Poul-Henning Kamp wrote:
    >In message <4365EF7B.1020706@freebsd.org>, David Xu writes:
    >>We can introduce
    >>hrtime_t clock_gethrtime(clockid_t clock) to get hi-resolution time
    >>as the one seen in RTLinux, or gethrtime() as seen in Solaris (Daniel
    >>Eischen said?)
    ...
    >The open group specifically allow clock_gettime() to implement
    >more timescales, so what did those fools go and invent even more
    >library functions for ?

    gethrtime() dates back to SunOS 4.x and (AFAIK) predates TOG's work.
    ISTR it's not really a syscall but just reads the HR clock out of
    the magic page with the timer.

    I'd also support a move to make gettimeofday() a cheaper syscall
    that counts in 1/hz and require the use of clock_gettime() for
    accurate timestamps.

    This still leaves the issue of the scheduler - do we need an accurate
    (and expensive) record of how long a particular process executes? We
    can probably make the timestamps slightly cheaper to obtain since we
    only need to keep track of a time difference on a single CPU - there's
    no need for inter-CPU synchronisation (because a thread can't migrate
    from from CPU to CPU without the scheduler knowing). It probably
    doesn't even matter if the time intervals provided to the scheduler
    are inaccurate by a few percent or differ slightly between CPUs.

    -- 
    Peter Jeremy
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Eric Hodel: "Re: MySQL Performance 6.0rc1"

    Relevant Pages

    • One minute delay when booting 2.6.24.1
      ... Switched to high resolution mode on CPU 1 ... io scheduler anticipatory registered ... # Infrared-port device drivers ...
      (Linux-Kernel)
    • [RFC][PATCH] O(1) Entitlement Based Scheduler
      ... This patch is a modification of the Oscheduler that introduces ... _entitlement_ to CPU resources that is determined by the number of _shares_ ... This patch provides both soft and hard CPU usage rate caps per ... one getting the most can be given a better priority, ...
      (Linux-Kernel)
    • Scheduler Economy prototype patch for CFS
      ... X should get more CPU time simply ... the clients, not relative to any client individually. ... today i've implemented a quick prototype of this "Scheduler Economy" ... * Scheduler work account object: it consists of the price, ...
      (Linux-Kernel)
    • Re: Re: OSDL Bug 3770
      ... We're discussing the fact that on SMP machines, ... N> CPU to be starved, while tasks on another CPU with the same low ... L> could had run on another CPU if the scheduler had decided otherwise). ... Does Linux tolerate hard CPU binding? ...
      (Linux-Kernel)
    • Re: [PATCH] CFS: sched-design-CFS.txt - ambiguity about leftmost and some formatting
      ... this is the CFS scheduler. ... precise multi-tasking CPU" on real hardware. ... disadvantage - the current task gets an unfair amount of CPU time. ... the task schedules (or a scheduler tick happens) the task's CPU usage is ...
      (Linux-Kernel)