Re: Call for performance evaluation: net.isr.direct (fwd)
From: Andrew Gallatin (gallatin_at_cs.duke.edu)
Date: 10/14/05
- Previous message: Doug Ambrisko: "bge BCM5721/BCM5750 fixes to work with IPMI"
- In reply to: Poul-Henning Kamp: "Re: Call for performance evaluation: net.isr.direct (fwd)"
- Next in thread: Poul-Henning Kamp: "Re: Call for performance evaluation: net.isr.direct (fwd)"
- Reply: Poul-Henning Kamp: "Re: Call for performance evaluation: net.isr.direct (fwd)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 14 Oct 2005 15:19:19 -0400 (EDT) To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Poul-Henning Kamp writes:
> The solution is not faster but less reliable timekeeping, the
> solution is to move the scheduler(s) away from using time as an
> approximation of cpu cycles.
So you mean rather than use binuptime() in mi_switch(), use some
per-cpu cycle counter (like rdtsc)?
Heck, why not just use ticks for the scheduler and keep the expensive
timekeeping code out of the critical path altogether? Does it really
need better than 1ms resolution?
Drew
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
- Previous message: Doug Ambrisko: "bge BCM5721/BCM5750 fixes to work with IPMI"
- In reply to: Poul-Henning Kamp: "Re: Call for performance evaluation: net.isr.direct (fwd)"
- Next in thread: Poul-Henning Kamp: "Re: Call for performance evaluation: net.isr.direct (fwd)"
- Reply: Poul-Henning Kamp: "Re: Call for performance evaluation: net.isr.direct (fwd)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]