All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Sightler <ttsig@tuxyturvy.com>
To: Lincoln Dale <ltd@cisco.com>
Cc: JG <jg@cms.ac>, Andreas Hartmann <andihartmann@freenet.de>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: TG3: very high CPU usage
Date: Thu, 22 Jan 2004 11:06:28 -0500	[thread overview]
Message-ID: <1074787587.5691.11.camel@localhost.localdomain> (raw)
In-Reply-To: <5.1.0.14.2.20040122143222.02a06d68@171.71.163.14>

On Wed, 2004-01-21 at 22:57, Lincoln Dale wrote:
> At 02:19 PM 21/01/2004, Tom Sightler wrote:
> >I'm curious is the people seeing this problem happen to have preempt
> >enabled in their config.  I've noticed that my laptop, which also
> >happens to have a tg3 based 10/100/1000 card, uses tons of CPU during
> >trasfers, but only when preempt is enabled.
> 
> nope.
> i didn't use PREEMPT=y in my previous test, but i have just done so now.
> 
> the difference in CPU utilization when pushing wire-rate gig-e ttcp on this 
> system (Dual P4 Xeon) with PREEMPT=y or PREEMPT=n is just noise.
> 
> you should run oprofile and see where your cpu time is spent.

Well, it was just a tought.  As it turns out in my case it seems the
problem was related to ACPI and PREEMPT (I still don't understand what
exactly).  Everything seems normal with ACPI without PREEMPT, or without
ACPI with PREEMPT, but if I enable both ACPI and PREEMPT I get a ton of
CPU usage.  In Fedora Core top it shows up as IRQ time.

I haven't run oprofile yet but it seems this problem is something to do
with ACPI and PREEMPT on my machine (perhaps something to do with IRQ
routing when ACPI is enabled).  Sounds like that doesn't apply to any of
the systems you guys are talking about.  Sorry for the noise.

PREEMPT with ACPI is showing some other problems on my machine as well
(for example when PREEMPT is enabled my battery status applet fails
after several hours of uptime, or even shorter if a stress the
network).  I can't reproduce this if I disable PREEMPT.

Anyway, good luck in finding a common issue for your problems.

Later,
Tom



  parent reply	other threads:[~2004-01-22 16:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19  3:35 TG3: very high CPU usage Mark Williams (MWP)
2004-01-20 12:33 ` JG
2004-01-20 23:13   ` Lincoln Dale
2004-01-21  3:19     ` Tom Sightler
2004-01-22  3:57       ` Lincoln Dale
2004-01-22 12:55         ` JG
2004-01-24 13:43           ` JG
2004-01-25  0:03             ` Lincoln Dale
2004-01-25 12:31               ` JG
2004-01-31  9:15                 ` JG
2004-02-01  0:20                   ` Lincoln Dale
2004-02-07 18:26                     ` JG
2004-02-08  0:00                       ` Lincoln Dale
2004-02-09 10:13                         ` JG
2004-01-22 16:06         ` Tom Sightler [this message]
     [not found] <fa.eu7l1gd.ekqe1j@ifi.uio.no>
2004-01-19 11:32 ` Andreas Hartmann
2004-01-20  3:54   ` Mark Williams (MWP)
     [not found] <fa.g9joqss.1nneajs@ifi.uio.no>
     [not found] ` <fa.e29fqcc.sick10@ifi.uio.no>
2004-01-20  9:17   ` Andreas Hartmann
2004-01-20  9:44     ` Lincoln Dale
2004-01-20 10:16       ` Mark Williams (MWP)
2004-01-20 12:09         ` Lincoln Dale

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=1074787587.5691.11.camel@localhost.localdomain \
    --to=ttsig@tuxyturvy.com \
    --cc=andihartmann@freenet.de \
    --cc=jg@cms.ac \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltd@cisco.com \
    /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.