From: "Lee Revell" <rlrevell@joe-job.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: "Michel Lespinasse" <walken@zoy.org>,
"Chuck Ebbert" <cebbert@redhat.com>,
linux-kernel@vger.kernel.org, "Dave Jones" <davej@redhat.com>,
"Jeb Cramer" <cramerj@intel.com>,
"John Ronciak" <john.ronciak@intel.com>,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
"Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
Subject: Re: 24 lost ticks with 2.6.20.10 kernel
Date: Tue, 1 May 2007 20:06:52 -0400 [thread overview]
Message-ID: <75b66ecd0705011706r3200fcecvff00953264325f30@mail.gmail.com> (raw)
In-Reply-To: <4637BA70.8000108@intel.com>
On 5/1/07, Kok, Auke <auke-jan.h.kok@intel.com> wrote:
> Michel Lespinasse wrote:
> > (I've added the E1000 maintainers to the thread as I found the issue
> > seems to go away after I compile out that driver. For reference, I was
> > trying to figure out why I lose exactly 24 ticks about every two
> > seconds, as shown with report_lost_ticks. This is with a DQ965GF
> > motherboard with onboard E1000).
>
> that's perfectly likely. The main issue is that we read the hardware stats every
> two seconds and that can consume quite some time. It's strange that you are
> losing that many ticks IMHO, but losing one or two might very well be.
>
Why do you have to disable all interrupts? Shouldn't it be sufficient
to disable interrupts on the e1000 only?
Lee
next prev parent reply other threads:[~2007-05-02 0:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 13:07 Michel Lespinasse
2007-05-01 15:34 ` Chuck Ebbert
2007-05-01 21:49 ` Michel Lespinasse
2007-05-01 22:08 ` Kok, Auke
2007-05-01 22:41 ` Chuck Ebbert
2007-05-01 22:45 ` Kok, Auke
2007-05-02 0:06 ` Lee Revell [this message]
2007-05-02 8:41 ` Michel Lespinasse
2007-05-02 16:07 ` Kok, Auke
2007-05-02 18:14 ` Kok, Auke
2007-05-03 6:27 ` e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel) Michel Lespinasse
2007-05-03 15:36 ` Kok, Auke
2007-05-03 15:56 ` Allan, Bruce W
2007-05-04 18:25 ` Kok, Auke
2007-05-04 21:15 ` Michel Lespinasse
2007-05-02 12:54 ` 24 lost ticks with 2.6.20.10 kernel Andi Kleen
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=75b66ecd0705011706r3200fcecvff00953264325f30@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=auke-jan.h.kok@intel.com \
--cc=cebbert@redhat.com \
--cc=cramerj@intel.com \
--cc=davej@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=walken@zoy.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
all inboxes | Powered by JetHome®