Re: ithread priority question...

From: Julian Elischer (julian_at_elischer.org)
Date: 06/23/04

  • Next message: Danny Pansters: "Re: "Maintaining your installation" question"
    Date: Tue, 22 Jun 2004 17:11:36 -0700 (PDT)
    To: Bosko Milekic <bmilekic@FreeBSD.org>
    
    

    On Tue, 22 Jun 2004, Bosko Milekic wrote:

    >
    > I'm obviously talking nonsense below. Sorry.
    >
    > The real explanation is that they are put on a runqueue when executed:
    >
    > if (TD_AWAITING_INTR(td)) {
    > CTR2(KTR_INTR, "%s: setrunqueue %d", __func__, p->p_pid);
    > TD_CLR_IWAIT(td);
    > setrunqueue(td);
    > if (do_switch &&
    > (ctd->td_critnest == 1) ) {
    > ...
    >
    > Sorry again!

    yes.. the question is.. does it make sense in a world with multiple
    schedulers to multiply set the priority of each ithread to
    (inumber * RQ_PPQ)?

    It happens to work with 4bsd and probably with ULE
    but it wouldn't make a lot of sense with (say) a monte-carlo scheduler
    that may not have run queues as such (such as Luigi did) or any
    scheduler for which RQ_PPQ was not a constant.

    >
    > -bosko
    >
    > Julian Elischer wrote:
    > >On Tue, 22 Jun 2004, John Baldwin wrote:
    > ...
    > >> That was the intention. One question though, if the ithreads aren't on the
    > >> system run queues then which run queues are they on?
    > >
    > >aren't they run from the interupt?
    >
    > Not always. They have to be put on a runqueue if they block on a
    > mutex, say.
    >
    > -Bosko
    >
    >

    _______________________________________________
    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: Danny Pansters: "Re: "Maintaining your installation" question"

    Relevant Pages

    • Linux SMT question
      ... our university started acquiring dual Xeon servers. ... Does this mean that if the scheduler puts different processes on the ... mapping CPU#0's runqueue to CPU#2's runqueue. ... I seem to remember hearing something about allocating a ...
      (Linux-Kernel)
    • Re: [PATCH 1/3] CPUMETER: add cpumeter framework to the CPUSETS
      ... >> the existing balancing code in the scheduler). ... it would be used for calculating load of each runqueue. ... Probably we can solve this issue by applying some weight to each tasks ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • [patch 63/76] sched: fix race in schedule()
      ... Fix a hard to trigger crash seen in the -rt kernel that also affects ... scheduler looks for another process on other CPU's runqueue because CPU1 ... dequeue_task(rq, tsk, 0); ...
      (Linux-Kernel)