On Friday 18 March 2011 04:11 pm, Kostik Belousov wrote:
> On Fri, Mar 18, 2011 at 02:09:58PM -0400, Jung-uk Kim wrote:
> > On Friday 18 March 2011 01:05 pm, Bruce Evans wrote:
> > > On Sat, 19 Mar 2011, Bruce Evans wrote:
> > > > On Fri, 18 Mar 2011, Kostik Belousov wrote:
> > > >> We definitely d
On Fri, Mar 18, 2011 at 02:09:58PM -0400, Jung-uk Kim wrote:
> On Friday 18 March 2011 01:05 pm, Bruce Evans wrote:
> > On Sat, 19 Mar 2011, Bruce Evans wrote:
> > > On Fri, 18 Mar 2011, Kostik Belousov wrote:
> > >> We definitely do not support configurations with different
> > >> models of CPUs i
On Friday 18 March 2011 01:05 pm, Bruce Evans wrote:
> On Sat, 19 Mar 2011, Bruce Evans wrote:
> > On Fri, 18 Mar 2011, Kostik Belousov wrote:
> >> We definitely do not support configurations with different
> >> models of CPUs in SMP, this is what Simmetric is about.
> >> Different as in frequency
On Sat, 19 Mar 2011, Bruce Evans wrote:
On Fri, 18 Mar 2011, Kostik Belousov wrote:
We definitely do not support configurations with different models of
CPUs in SMP, this is what Simmetric is about. Different as in frequency
or stepping.
...
Now there is even more asymmetry
in core frequencie
On Friday 18 March 2011 12:15 pm, Kostik Belousov wrote:
> On Fri, Mar 18, 2011 at 05:51:27PM +0200, Andriy Gapon wrote:
> > on 18/03/2011 15:56 Kostik Belousov said the following:
> > > On Fri, Mar 18, 2011 at 05:26:53PM +1100, Bruce Evans wrote:
> > > ...
> > >
> > >> - set cputicker() has some d
On Fri, 18 Mar 2011, Kostik Belousov wrote:
On Fri, Mar 18, 2011 at 05:26:53PM +1100, Bruce Evans wrote:
...
- set cputicker() has some design bugs. It assumes that the tick frequency
is the same across all CPUs, but the TSC is per-CPU. I have an old SMP
system with CPUs of different freq
On Fri, Mar 18, 2011 at 05:51:27PM +0200, Andriy Gapon wrote:
> on 18/03/2011 15:56 Kostik Belousov said the following:
> > On Fri, Mar 18, 2011 at 05:26:53PM +1100, Bruce Evans wrote:
> > ...
> >> - set cputicker() has some design bugs. It assumes that the tick frequency
> >> is the same across
on 18/03/2011 15:56 Kostik Belousov said the following:
> On Fri, Mar 18, 2011 at 05:26:53PM +1100, Bruce Evans wrote:
> ...
>> - set cputicker() has some design bugs. It assumes that the tick frequency
>> is the same across all CPUs, but the TSC is per-CPU. I have an old SMP
>> system with C
On Fri, Mar 18, 2011 at 05:26:53PM +1100, Bruce Evans wrote:
...
> - set cputicker() has some design bugs. It assumes that the tick frequency
> is the same across all CPUs, but the TSC is per-CPU. I have an old SMP
> system with CPUs of different frequency that can demonstrate bugs from
> t
On Thu, 17 Mar 2011, Jung-uk Kim wrote:
Both get_cyclecount(9) and cpu_ticks() do almost exactly the same
thing now assuming set_cputicker() is called with a correct function
before get_cyclecount() is used, which is true for x86, at least.
The only difference is get_cyclecount() may be inlined
10 matches
Mail list logo