From: "David S. Miller" <davem@redhat.com>
To: Stephen Lee <mukansai@emailplus.org>
Cc: laforge@netfilter.org, netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: Extremely slow network with e1000 & ip_conntrack
Date: Tue, 2 Dec 2003 21:03:37 -0800 [thread overview]
Message-ID: <20031202210337.5dda502f.davem@redhat.com> (raw)
In-Reply-To: <20031202204404.9ADD.MUKANSAI@emailplus.org>
On Tue, 02 Dec 2003 20:44:06 +0900
Stephen Lee <mukansai@emailplus.org> wrote:
> After lots of trial-and-error, I can make the problem disappear by
> backing these 4 files out from 2.5.44 to their 2.5.43 versions.
>
> net/ipv4/icmp.c
> net/ipv4/ip_output.c
> net/ipv4/raw.c
> net/ipv4/udp.c
Interesting, but not very. This essentially backs out the whole
ipv4 packet sending engine rewrite we did to support IPSEC and
UDP sendfile support.
Ie. it's a lot of large interrelated changes. We know now what
introduced the problem, but this hasn't really narrowed it down
much.
next prev parent reply other threads:[~2003-12-03 5:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 8:49 Extremely slow network with e1000 & ip_conntrack Stephen Lee
2003-11-28 19:55 ` Stephen Lee
2003-11-29 22:54 ` Stephen Lee
2003-11-30 15:52 ` Harald Welte
2003-12-02 11:44 ` Stephen Lee
2003-12-03 5:03 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 6:51 Feldman, Scott
2003-12-04 12:36 ` Stephen Lee
2003-12-04 18:24 ` David S. Miller
2003-12-05 20:45 ` Stephen Lee
2003-12-05 20:28 ` David S. Miller
2003-12-05 22:20 ` Stephen Lee
2003-12-05 22:56 ` David S. Miller
2003-12-11 7:26 ` Harald Welte
2003-12-11 8:25 ` Henrik Nordstrom
2003-12-04 7:24 Feldman, Scott
2003-12-04 17:37 Feldman, Scott
2003-12-04 18:30 ` David S. Miller
2003-12-04 19:53 ` Stephen Lee
2003-12-04 20:09 ` Jeff Garzik
2003-12-05 13:25 ` Stephen Lee
2003-12-04 20:20 ` David S. Miller
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=20031202210337.5dda502f.davem@redhat.com \
--to=davem@redhat.com \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukansai@emailplus.org \
--cc=netfilter-devel@lists.netfilter.org \
/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.