Re: Scheduler fixes for hyperthreading
From: Colin Percival (cperciva_at_freebsd.org)
Date: 05/22/05
- Previous message: Marcel Moolenaar: "Re: Scheduler fixes for hyperthreading"
- In reply to: Marcel Moolenaar: "Re: Scheduler fixes for hyperthreading"
- Next in thread: Sam Lawrance: "Re: Scheduler fixes for hyperthreading"
- Reply: Sam Lawrance: "Re: Scheduler fixes for hyperthreading"
- Reply: Marcel Moolenaar: "Re: Scheduler fixes for hyperthreading"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 21 May 2005 21:35:13 -0700 To: Marcel Moolenaar <marcel@xcllnt.net>
Marcel Moolenaar wrote:
> There are a lot of variables that need to be taken into account and
> those variables do not necessarily map perfectly from a P4 to an I2.
> Sharing of the L1 cache is not a sufficient condition to create a
> side-channel for timing attacks. A reliable time source with enough
> precision is also necessary (as you and Stephan have pointed out).
> The precision of the time source depends on latencies of the various
> cache levels and the micro-architectural behavior of the processor.
Point taken. I maintain, however, that it is much better to make
"information can leak between these processors" a machine-independent
concept which is handled appropriately by the scheduler (with the
necessary machine-dependent code to specify *which* sets of processors,
if any, have such leakage).
Colin Percival
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Marcel Moolenaar: "Re: Scheduler fixes for hyperthreading"
- In reply to: Marcel Moolenaar: "Re: Scheduler fixes for hyperthreading"
- Next in thread: Sam Lawrance: "Re: Scheduler fixes for hyperthreading"
- Reply: Sam Lawrance: "Re: Scheduler fixes for hyperthreading"
- Reply: Marcel Moolenaar: "Re: Scheduler fixes for hyperthreading"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: Scheduler fixes for hyperthreading
... >> Sharing of the L1 cache is not a sufficient condition to create a ...
>> precision is also necessary. ... (freebsd-arch) - Re: Fastcode RoundTo B&V 0.1
... You could cache an array of extended (Int64 only ... an extended
type cannot hold the precision and ... (borland.public.delphi.language.basm) - Re: www.sicortex.com
... FPU was optimized toward single-precision performance. ... double precision
at 2FLOPs per cycle (MADD.D a double precision ... For massively-parallel scientific workloads
ECC (if it is actually ... ECC) on L1D cache sounds to me like over-engineering. ...
(comp.arch)