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: Tue, 20 Jan 2004 22:19:22 -0500	[thread overview]
Message-ID: <1074655162.5834.16.camel@localhost.localdomain> (raw)
In-Reply-To: <5.1.0.14.2.20040121100550.03cff190@171.71.163.14>

On Tue, 2004-01-20 at 18:13, Lincoln Dale wrote:
> At 11:33 PM 20/01/2004, JG wrote:
> >i have also two boxes (one with 2.6.0, the other one 2.6.1-mm2) equipped 
> >with netgear ga302t cards (x-over cable).
> >i don't see a very high cpu usage, but since upgrading to 2.6.x kernels i 
> >sometimes have really weird speed issues. i often only get transfer rates 
> >of about ~200-300 kilobytes/second...yes, and this over a gigabit 
> >interface, tested over ftp.
> >i'm also running a nfs server on the 2.6.1-mm2 box, the 2.6.0 pc is the 
> >client, but again, sometimes it's *very* slow. if i reboot my 2.6.1-mm2 
> >box (the other one is a server which can't be rebooted) it seems to be 
> >fine for some time.
> >
> >i didn't have such problems with 2.4.19 kernels on both pcs, there i got 
> >about 30-35MB/s over ftp without any problems, so i don't think it's 
> >hardware related.

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.

After looking into this, my Aironet wireless has exactly the same
problem.  When preempt is enabled a simple scp transfer running at
approximately maximum speed for 802.11b (7.5Mb/sec) uses almost 70% of
the CPU.  The tg3 driver doing the same scp at 40Mb/sec (100Mb ethernet)
uses > 90% of the CPU.

However, turning off preempt and my system runs at approximately the
same speed on wireless (7.5Mb/sec) but only about 5% CPU.  The tg3
driver with preempt disabled allows the scp to run at near wire speed
(95-100Mb/sec) and uses only a fraction of the CPU.

Just curious if this might be what others are seeing.

Later,
Tom



  reply	other threads:[~2004-01-21  3:19 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 [this message]
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
     [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=1074655162.5834.16.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.