xcal are sometimes a signature of some problem. Of
themselves they should be cheap. Below one sees that the sys
time is rather small, so I'm inclined to think this is not a
problem here pending further analysis of the problem. We see
that all you CPUs are making what appears to progress
On Thu, Oct 18, 2007 at 10:32:58AM -0500, Mike Gerdts wrote:
> On 10/18/07, Gary Mills <[EMAIL PROTECTED]> wrote:
> > What's the command to show cross calls?
>
> mpstat will show it on a system basis.
Thanks. This is on our T2000 Cyrus IMAP server with ZFS. It's
the second listing from `mpstat
Gary Mills wrote:
> What's the command to show cross calls?
mpstat
--
Michael SchusterSun Microsystems, Inc.
recursion, n: see 'recursion'
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zf
On Thu, 18 Oct 2007, Mike Gerdts wrote:
> On 10/18/07, Bill Sommerfeld <[EMAIL PROTECTED]> wrote:
>> that sounds like a somewhat mangled description of the cross-calls done
>> to invalidate the TLB on other processors when a page is unmapped.
>> (it certainly doesn't happen on *every* update to a
On 10/18/07, Gary Mills <[EMAIL PROTECTED]> wrote:
> What's the command to show cross calls?
mpstat will show it on a system basis.
xcallsbypid.d from the DTraceToolkit (ask google) will tell you which
PID is responsible.
--
Mike Gerdts
http://mgerdts.blogspot.com/
_
>
> What's the command to show cross calls?
>
mpstat(1M)
example o/p
$ mpstat 1
CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl
0 16 0 0 416 316 485 16 0 0 0 618 7 3 0 90
0 6 0 0 425 324 488 2 0 0 0 579 4 2 0 94
___
zfs-disc
On Thu, Oct 18, 2007 at 10:16:52AM -0400, Bill Sommerfeld wrote:
> On Thu, 2007-10-18 at 08:04 -0500, Gary Mills wrote:
> > Here's a suggestion on the cause:
> >
> > The root problem seems to be an interaction between Solaris' concept
> > of global memory consistency and the fact that Cyrus sp
On 10/18/07, Bill Sommerfeld <[EMAIL PROTECTED]> wrote:
> that sounds like a somewhat mangled description of the cross-calls done
> to invalidate the TLB on other processors when a page is unmapped.
> (it certainly doesn't happen on *every* update to a mapped file).
I've seen systems running Verit
On Thu, 2007-10-18 at 08:04 -0500, Gary Mills wrote:
> Here's a suggestion on the cause:
>
> The root problem seems to be an interaction between Solaris' concept
> of global memory consistency and the fact that Cyrus spawns many
> processes that all memory map (mmap) the same file. Whenever
Does anyone on this mailing list have an idea what went wrong with
ZFS and Cyrus IMAP? Here's an excerpt that explains the problem:
About a week before classes actually start is when all the kids start
moving back into town and mailing all their buds. We saw process
numbers go from 500-ish
10 matches
Mail list logo
