All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
	"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>,
	pravin b shelar <pravin.shelar@calsoftinc.com>
Subject: Re: High lock spin time for zone->lru_lock under extreme conditions
Date: Fri, 12 Jan 2007 23:36:43 -0800	[thread overview]
Message-ID: <20070113073643.GA4234@localhost.localdomain> (raw)
In-Reply-To: <45A86291.8090408@yahoo.com.au>

On Sat, Jan 13, 2007 at 03:39:45PM +1100, Nick Piggin wrote:
> Ravikiran G Thirumalai wrote:
> >Hi,
> >We noticed high interrupt hold off times while running some memory 
> >intensive
> >tests on a Sun x4600 8 socket 16 core x86_64 box.  We noticed softlockups,
> 
> [...]
> 
> >We did not use any lock debugging options and used plain old rdtsc to
> >measure cycles.  (We disable cpu freq scaling in the BIOS). All we did was
> >this:
> >
> >void __lockfunc _spin_lock_irq(spinlock_t *lock)
> >{
> >        local_irq_disable();
> >        ------------------------> rdtsc(t1);
> >        preempt_disable();
> >        spin_acquire(&lock->dep_map, 0, 0, _RET_IP_);
> >        _raw_spin_lock(lock);
> >        ------------------------> rdtsc(t2);
> >        if (lock->spin_time < (t2 - t1))
> >                lock->spin_time = t2 - t1;
> >}
> >
> >On some runs, we found that the zone->lru_lock spun for 33 seconds or more
> >while the maximal CS time was 3 seconds or so.
> 
> What is the "CS time"?

Critical Section :).  This is the maximal time interval I measured  from 
t2 above to the time point we release the spin lock.  This is the hold 
time I guess.

> 
> It would be interesting to know how long the maximal lru_lock *hold* time 
> is,
> which could give us a better indication of whether it is a hardware problem.
> 
> For example, if the maximum hold time is 10ms, that it might indicate a
> hardware fairness problem.

The maximal hold time was about 3s.

WARNING: multiple messages have this Message-ID (diff)
From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
	"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>,
	pravin b shelar <pravin.shelar@calsoftinc.com>
Subject: Re: High lock spin time for zone->lru_lock under extreme conditions
Date: Fri, 12 Jan 2007 23:36:43 -0800	[thread overview]
Message-ID: <20070113073643.GA4234@localhost.localdomain> (raw)
In-Reply-To: <45A86291.8090408@yahoo.com.au>

On Sat, Jan 13, 2007 at 03:39:45PM +1100, Nick Piggin wrote:
> Ravikiran G Thirumalai wrote:
> >Hi,
> >We noticed high interrupt hold off times while running some memory 
> >intensive
> >tests on a Sun x4600 8 socket 16 core x86_64 box.  We noticed softlockups,
> 
> [...]
> 
> >We did not use any lock debugging options and used plain old rdtsc to
> >measure cycles.  (We disable cpu freq scaling in the BIOS). All we did was
> >this:
> >
> >void __lockfunc _spin_lock_irq(spinlock_t *lock)
> >{
> >        local_irq_disable();
> >        ------------------------> rdtsc(t1);
> >        preempt_disable();
> >        spin_acquire(&lock->dep_map, 0, 0, _RET_IP_);
> >        _raw_spin_lock(lock);
> >        ------------------------> rdtsc(t2);
> >        if (lock->spin_time < (t2 - t1))
> >                lock->spin_time = t2 - t1;
> >}
> >
> >On some runs, we found that the zone->lru_lock spun for 33 seconds or more
> >while the maximal CS time was 3 seconds or so.
> 
> What is the "CS time"?

Critical Section :).  This is the maximal time interval I measured  from 
t2 above to the time point we release the spin lock.  This is the hold 
time I guess.

> 
> It would be interesting to know how long the maximal lru_lock *hold* time 
> is,
> which could give us a better indication of whether it is a hardware problem.
> 
> For example, if the maximum hold time is 10ms, that it might indicate a
> hardware fairness problem.

The maximal hold time was about 3s.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-01-13  7:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 16:01 High lock spin time for zone->lru_lock under extreme conditions Ravikiran G Thirumalai
2007-01-12 16:01 ` Ravikiran G Thirumalai
2007-01-12 17:03 ` Peter Zijlstra
2007-01-12 17:03   ` Peter Zijlstra
2007-01-12 19:46 ` Christoph Lameter
2007-01-12 19:46   ` Christoph Lameter
2007-01-12 21:25   ` Andrew Morton
2007-01-12 21:25     ` Andrew Morton
2007-01-12 21:40   ` Ravikiran G Thirumalai
2007-01-12 21:40     ` Ravikiran G Thirumalai
2007-01-12 21:45     ` Christoph Lameter
2007-01-12 21:45       ` Christoph Lameter
2007-01-13  1:00       ` Ravikiran G Thirumalai
2007-01-13  1:00         ` Ravikiran G Thirumalai
2007-01-13  1:11         ` Andrew Morton
2007-01-13  1:11           ` Andrew Morton
2007-01-13  7:42           ` Ravikiran G Thirumalai
2007-01-13  7:42             ` Ravikiran G Thirumalai
2007-01-13  4:39 ` Nick Piggin
2007-01-13  4:39   ` Nick Piggin
2007-01-13  7:36   ` Ravikiran G Thirumalai [this message]
2007-01-13  7:36     ` Ravikiran G Thirumalai
2007-01-13  7:53     ` Nick Piggin
2007-01-13  7:53       ` Nick Piggin
2007-01-13  8:00     ` Andrew Morton
2007-01-13  8:00       ` Andrew Morton
2007-01-13 19:53       ` Ravikiran G Thirumalai
2007-01-13 19:53         ` Ravikiran G Thirumalai
2007-01-13 21:20         ` Andrew Morton
2007-01-13 21:20           ` Andrew Morton
2007-01-16  2:56           ` Ravikiran G Thirumalai
2007-01-16  2:56             ` Ravikiran G Thirumalai

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=20070113073643.GA4234@localhost.localdomain \
    --to=kiran@scalex86.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pravin.shelar@calsoftinc.com \
    --cc=shai@scalex86.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.