Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: mlachwani <mlachwani@mvista.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: m_lachwani@yahoo.com, creideiki+linux-mips@ferretporn.se,
	ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: Extreme system overhead on large IP27
Date: Thu, 26 Oct 2006 18:55:03 -0700	[thread overview]
Message-ID: <454166F7.70200@mvista.com> (raw)
In-Reply-To: <20061026.231642.126142599.anemo@mba.ocn.ne.jp>

Hi Atsushi,

I tried out your patch on the SWARM SMP and it works.

thanks,
Manish Lachwani

Atsushi Nemoto wrote:
> On Thu, 26 Oct 2006 00:42:16 -0700 (PDT), Manish Lachwani <m_lachwani@yahoo.com> wrote:
>   
>> It could be that I am seeing a similar issue on the
>> SWARM board (sb1250) as well. Your patch removed the
>> shifts for mip_hpt_frequency from
>> arch/mips/sibyte/sb1250/time.c and in the
>> sb1250_hpt_read(). The Sibyte HPT is 1 Mhz. However,
>> when I added those shifts back, I did not see any
>> issues with the system clock. I could possibly try out
>> your patch with lower clocksource shift values and see
>> if the system clock is still wrong.
>>     
>
> I just sent the patch.  Please try it.
>
>   
>> Btw, the clocksource changes seem to work well on the
>> BCM 1480 based board. 
>>     
>
> Thanks, good news!
>
> As Ralf pointed out, current code still problematic on some SMP
> system, but I think IP27, SB1250, BCM1480 should be OK now while their
> mips_hpt_read are not using per-CPU cp0 timers.
>
> ---
> Atsushi Nemoto
>
>   

  reply	other threads:[~2006-10-27  1:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21 19:59 Extreme system overhead on large IP27 Karl-Johan Karlsson
2006-10-22 15:21 ` Ralf Baechle
2006-10-22 23:23   ` Ralf Baechle
2006-10-23  0:19     ` Ralf Baechle
2006-10-23 21:30       ` Karl-Johan Karlsson
     [not found]         ` <20061023224318.GA1732@linux-mips.org>
2006-10-24 13:53           ` Karl-Johan Karlsson
2006-10-24 14:06             ` Ralf Baechle
2006-10-24 15:33               ` Ilya A. Volynets-Evenbakh
2006-10-24 15:44               ` Karl-Johan Karlsson
2006-10-24 15:50                 ` Ralf Baechle
2006-10-24 17:34                 ` Atsushi Nemoto
2006-10-24 17:50                   ` Ralf Baechle
2006-10-25  8:45                 ` Atsushi Nemoto
2006-10-26  4:05                   ` Atsushi Nemoto
2006-10-26  7:42                     ` Manish Lachwani
2006-10-26 14:16                       ` Atsushi Nemoto
2006-10-27  1:55                         ` mlachwani [this message]
2006-10-26  8:41                     ` Karl-Johan Karlsson
2006-10-26 12:56                     ` Ralf Baechle
2006-10-26 13:51                       ` Kevin D. Kissell
2006-10-26 13:51                         ` Kevin D. Kissell
2006-10-26 16:50                         ` Ralf Baechle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=454166F7.70200@mvista.com \
    --to=mlachwani@mvista.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=creideiki+linux-mips@ferretporn.se \
    --cc=linux-mips@linux-mips.org \
    --cc=m_lachwani@yahoo.com \
    --cc=ralf@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox