From: Eric Dumazet <dada1@cosmosbay.com>
To: Michael Chan <mchan@broadcom.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: [TG3]: About hw coalescing infrastructure.
Date: Mon, 04 Jul 2005 23:22:12 +0200 [thread overview]
Message-ID: <42C9A884.1030906@cosmosbay.com> (raw)
In-Reply-To: <1119467012.5325.15.camel@rh4>
Michael Chan a écrit :
> On Wed, 2005-06-22 at 17:25 +0200, Eric Dumazet wrote:
>
>
>>Is there anything I can try to tune the coalescing ?
>>Being able to handle 100 packets each interrupt instead of one or two would certainly help.
>>I dont mind about latency. But of course I would like not to drop packets :)
>>But maybe the BCM5702 is not able to delay an interrupt ?
>>
>
>
> On the 5702 that supports CLRTCKS mode, you need to play around with the
> following parameters in tg3.h. To reduce interrupts, you generally have
> to increase the values.
>
> #define LOW_RXCOL_TICKS_CLRTCKS 0x00000014
> #define LOW_TXCOL_TICKS_CLRTCKS 0x00000048
> #define LOW_RXMAX_FRAMES 0x00000005
> #define LOW_TXMAX_FRAMES 0x00000035
> #define DEFAULT_RXCOAL_TICK_INT_CLRTCKS 0x00000014
> #define DEFAULT_TXCOAL_TICK_INT_CLRTCKS 0x00000014
> #define DEFAULT_RXCOAL_MAXF_INT 0x00000005
> #define DEFAULT_TXCOAL_MAXF_INT 0x00000005
>
>
>
Thanks Michael
I tried various settings.
# ethtool -c eth0
Coalesce parameters for eth0:
Adaptive RX: off TX: off
stats-block-usecs: 1000000
sample-interval: 0
pkt-rate-low: 0
pkt-rate-high: 0
rx-usecs: 500
rx-frames: 20
rx-usecs-irq: 500
rx-frames-irq: 20
tx-usecs: 600
tx-frames: 53
tx-usecs-irq: 600
tx-frames-irq: 20
rx-usecs-low: 0
rx-frame-low: 0
tx-usecs-low: 0
tx-frame-low: 0
rx-usecs-high: 0
rx-frame-high: 0
tx-usecs-high: 0
tx-frame-high: 0
But it seems something is wrong because when network load becomes high I get :
Jul 4 23:01:19 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:19 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:01:24 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:24 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:01:29 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:29 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:01:34 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:34 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:01:39 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:39 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:01:44 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:44 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:01:49 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:49 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:01:54 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:54 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:01:59 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:01:59 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:02:04 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:02:04 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:02:09 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:02:09 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:02:14 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:02:14 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:02:19 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:02:19 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:02:24 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:02:24 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:02:29 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:02:29 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:02:34 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:02:34 dada1 kernel: tg3: eth0: transmit timed out, resetting
Jul 4 23:02:39 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 4 23:02:39 dada1 kernel: tg3: eth0: transmit timed out, resetting
Then the machine crashes at this point.
tg3.c :
#define DRV_MODULE_VERSION "3.31"
#define DRV_MODULE_RELDATE "June 8, 2005"
# ethtool -g eth0
Ring parameters for eth0:
Pre-set maximums:
RX: 511
RX Mini: 0
RX Jumbo: 255
TX: 0
Current hardware settings:
RX: 400
RX Mini: 0
RX Jumbo: 40
TX: 511
Thank you
Eric Dumazet
next prev parent reply other threads:[~2005-07-04 21:22 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 21:15 [TG3]: Add hw coalescing infrastructure David S. Miller
2005-05-11 21:17 ` Michael Chan
2005-05-12 2:28 ` David S. Miller
2005-05-12 7:53 ` Robert Olsson
2005-06-22 15:25 ` [TG3]: About " Eric Dumazet
2005-06-22 19:03 ` Michael Chan
2005-07-04 21:22 ` Eric Dumazet [this message]
2005-07-04 21:26 ` David S. Miller
2005-07-04 21:39 ` Eric Dumazet
2005-07-04 21:49 ` David S. Miller
2005-07-04 22:31 ` Eric Dumazet
2005-07-04 22:47 ` David S. Miller
2005-07-04 22:55 ` Eric Dumazet
2005-07-04 22:57 ` Eric Dumazet
2005-07-04 23:01 ` David S. Miller
2005-07-05 7:38 ` [PATCH] loop unrolling in net/sched/sch_generic.c Eric Dumazet
2005-07-05 11:51 ` Thomas Graf
2005-07-05 12:03 ` Thomas Graf
2005-07-05 13:04 ` Eric Dumazet
2005-07-05 13:48 ` Thomas Graf
2005-07-05 15:58 ` Eric Dumazet
2005-07-05 17:34 ` Thomas Graf
2005-07-05 21:22 ` David S. Miller
2005-07-05 21:33 ` Thomas Graf
2005-07-05 21:35 ` David S. Miller
2005-07-05 23:16 ` Eric Dumazet
2005-07-05 23:41 ` Thomas Graf
2005-07-05 23:45 ` David S. Miller
2005-07-05 23:55 ` Thomas Graf
2005-07-06 0:32 ` Eric Dumazet
2005-07-06 0:51 ` Thomas Graf
2005-07-06 1:04 ` Eric Dumazet
2005-07-06 1:07 ` Thomas Graf
2005-07-06 0:53 ` Eric Dumazet
2005-07-06 1:02 ` Thomas Graf
2005-07-06 1:09 ` Eric Dumazet
2005-07-06 12:42 ` Thomas Graf
2005-07-07 21:17 ` David S. Miller
2005-07-07 21:34 ` Thomas Graf
2005-07-07 22:24 ` David S. Miller
[not found] ` <42CE22CE.7030902@cosmosbay.com>
2005-07-08 7:30 ` David S. Miller
2005-07-08 8:19 ` Eric Dumazet
2005-07-08 11:08 ` Arnaldo Carvalho de Melo
2005-07-12 4:02 ` David S. Miller
2005-07-05 21:26 ` David S. Miller
2005-07-28 15:52 ` [PATCH] Add prefetches in net/ipv4/route.c Eric Dumazet
2005-07-28 19:39 ` David S. Miller
2005-07-28 20:56 ` Eric Dumazet
2005-07-28 20:58 ` David S. Miller
2005-07-28 21:24 ` Eric Dumazet
2005-07-28 22:44 ` David S. Miller
2005-07-29 14:50 ` Robert Olsson
2005-07-29 17:06 ` Rick Jones
2005-07-29 17:44 ` Robert Olsson
2005-07-29 17:57 ` Eric Dumazet
2005-07-29 18:25 ` Rick Jones
2005-07-31 3:52 ` David S. Miller
[not found] ` <42EDDA50.4010405@cosmosbay.com>
2005-08-01 15:39 ` David S. Miller
2005-07-31 3:51 ` David S. Miller
2005-07-31 3:44 ` David S. Miller
2005-07-04 23:00 ` [TG3]: About hw coalescing infrastructure David S. Miller
2005-07-05 16:14 ` Eric Dumazet
2005-07-04 22:47 ` Eric Dumazet
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=42C9A884.1030906@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@oss.sgi.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.