From: Christopher Chan <cchan@outblaze.com>
To: Christopher Chan <cchan@outblaze.com>
Cc: Scott Feldman <scott.feldman@intel.com>,
jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6] e100: use NAPI mode all the time
Date: Wed, 16 Jun 2004 02:04:37 +0800 [thread overview]
Message-ID: <40CF3A35.3070906@outblaze.com> (raw)
In-Reply-To: <40C58CA2.4090107@outblaze.com>
Christopher Chan wrote:
> Scott Feldman wrote:
>
>> I see no reason to keep the non-NAPI option for e100. This patch removes
>> the CONFIG_E100_NAPI option and puts the driver in NAPI mode all the
>> time.
>> Matches the way tg3 works.
>>
>> Unless someone has a really good reason to keep the non-NAPI mode, this
>> should go in for 2.6.7.
>
>
> I for one need to test 2.6.6 e100 with NAPI on. Under 2.6.3/4 I had
> problems with NAPI mode turned on. Turning NAPI off and then also doing
>
> net.ipv4.tcp_max_syn_backlog = 2048
> net.ipv4.route.gc_thresh = 65536
> net.ipv4.route.max_size = 1048576
>
> was the only way to keep the machines I run available via the network.
>
> I would get dst cache overflows and sometimes the kernel will log
> garbled messages and when that happens the box requires a reboot.
>
KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & (MSG_PEEK |
MSG_TRUNC))) failed at net/ipv4/tcp.c (1632)
KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1568)
KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & (MSG_PEEK |
MSG_TRUNC))) failed at net/ipv4/tcp.c (1632)
KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1568)
printk: 4253 messages suppressed.
dst cache overflow
KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & (MSG_PEEK |
MSG_TRUNC))) failed at net/ipv4/tcp.c (1632)
KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1568)
KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & (MSG_PEEK |
MSG_TRUNC))) failed at net/ipv4/tcp.c (1632)
KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1568)
KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & (MSG_PEEK |
MSG_TRUNC))) failed at net/ipv4/tcp.c (1632)
KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1568)
KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & (MSG_PEEK |
MSG_TRUNC))) failed at net/ipv4/tcp.c (1632)
I get loads of this now for the only box that I have NAPI enabled on the
e100 driver.
This is on a 2.6.6 kernel.
next prev parent reply other threads:[~2004-06-15 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 0:35 [PATCH 2.6] e100: use NAPI mode all the time Scott Feldman
2004-06-06 22:57 ` Tim Mattox
2004-06-07 0:03 ` Scott Feldman
2004-06-07 1:51 ` Tim Mattox
2004-06-07 2:33 ` Jeff Garzik
2004-06-07 6:39 ` [Bonding-devel] " Jay Vosburgh
2004-06-07 11:17 ` jamal
2004-06-08 9:53 ` Christopher Chan
2004-06-15 18:04 ` Christopher Chan [this message]
2004-06-11 0:16 ` Jeff Garzik
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=40CF3A35.3070906@outblaze.com \
--to=cchan@outblaze.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).