[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75b66ecd0705011706r3200fcecvff00953264325f30@mail.gmail.com>
Date: Tue, 1 May 2007 20:06:52 -0400
From: "Lee Revell" <rlrevell@...-job.com>
To: "Kok, Auke" <auke-jan.h.kok@...el.com>
Cc: "Michel Lespinasse" <walken@....org>,
"Chuck Ebbert" <cebbert@...hat.com>, linux-kernel@...r.kernel.org,
"Dave Jones" <davej@...hat.com>, "Jeb Cramer" <cramerj@...el.com>,
"John Ronciak" <john.ronciak@...el.com>,
"Jesse Brandeburg" <jesse.brandeburg@...el.com>,
"Jeff Kirsher" <jeffrey.t.kirsher@...el.com>
Subject: Re: 24 lost ticks with 2.6.20.10 kernel
On 5/1/07, Kok, Auke <auke-jan.h.kok@...el.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists