Re: rusage breakdown and cpu limits.

* Jeff Roberson <jroberson@xxxxxxxxxxxxxx> [070529 11:07] wrote:
I'm working with Attilio to break down rusage further to be per-thread in
places where it is protected by the global scheduler lock. To support
this, I am interested in moving the rlimit cpulimit check into userret(),
or perhaps ast(). Is there any reason why we need to check this on every
context switch? Any objections to moving it? Eventually it will require
a different lock from the one we obtain to call mi_switch().

Er, as long as it's checked each place where we can issue a signal
so a SIGXCPU can be sent when tsleep/cv_wait_sig...

right?

-Alfred
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: rusage breakdown and cpu limits.
    ... On Tue, 29 May 2007, John Baldwin wrote: ... Any objections to moving it? ... The only reason to not move the check into userret() ... For multithreaded processes this will give the same contention as a global scheduler lock, ...
    (freebsd-arch)
  • Re: rusage breakdown and cpu limits.
    ... this, I am interested in moving the rlimit cpulimit check into userret, ... Any objections to moving it? ... For multithreaded processes this will give the same contention as a global scheduler lock, ... I think I'm going to make the rusage struct per-thread and aggregate it on demand. ...
    (freebsd-arch)
  • Re: rusage breakdown and cpu limits.
    ... places where it is protected by the global scheduler lock. ... To support ... this, I am interested in moving the rlimit cpulimit check into userret, ... Any objections to moving it? ...
    (freebsd-arch)
  • rusage breakdown and cpu limits.
    ... I'm working with Attilio to break down rusage further to be per-thread in places where it is protected by the global scheduler lock. ... To support this, I am interested in moving the rlimit cpulimit check into userret, or perhaps ast. ...
    (freebsd-arch)