From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9ab217670704170939w367bdaa5na862dc6bb7e4b903@mail.gmail.com>
Date: Tue, 17 Apr 2007 12:39:01 -0400
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] syscall spikes
In-Reply-To: <9ab217670704170929l5f8f551bl6c076fbce7d89cac@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9ab217670704170838g363bba09pc0328e13106d0efd@mail.gmail.com>
	<61909b30c2fd4aed1dc3174595a1e4a7@coraid.com>
	<9ab217670704170856y7bf2265dl8cf121926232f905@mail.gmail.com>
	<9ab217670704170929l5f8f551bl6c076fbce7d89cac@mail.gmail.com>
Topicbox-Message-UUID: 4ba4c844-ead2-11e9-9d60-3106f5b1d025

2007/4/17, Devon H. O'Dell <devon.odell@gmail.com>:
> Steve Simon suggested the problem was timesync. He seems to have been
> very correct in this suggestion. Though I wonder why it needs to do >
> 60k syscalls :\.

And my apologies for continuing additions to this thread and flooding
the inboxes of you fine subscribers :\. It seems that somehow I ended
up with 2 timesyncs running. This causes the spikes I was seeing -- a
single timesync doesn't spike terribly badly.

Should there be some check in timesync to prevent two from running?
There should be no reason for this to ever occur.

--dho