From: "David S. Miller" <davem@redhat.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: mukansai@emailplus.org, laforge@netfilter.org,
netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: Extremely slow network with e1000 & ip_conntrack
Date: Thu, 4 Dec 2003 10:30:41 -0800 [thread overview]
Message-ID: <20031204103041.21aefd8d.davem@redhat.com> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0102CBDD21@orsmsx402.jf.intel.com>
On Thu, 4 Dec 2003 09:37:19 -0800
"Feldman, Scott" <scott.feldman@intel.com> wrote:
> TSO is support on 82540. Turning off TSO is a workaround, but what's
> behind the dependency of TSO and ip_conntrack?
Netfilter wants to see the _real_ packets that will be sent onto the
wire. TSO is a template by which to create such packets, not the real
thing.
So when and if we go into netfilter, we must un-TSO the packet so
that netfilter can look at what it really wants to.
next prev parent reply other threads:[~2003-12-04 18:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 17:37 Extremely slow network with e1000 & ip_conntrack Feldman, Scott
2003-12-04 18:30 ` David S. Miller [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 7:24 Feldman, Scott
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-11-26 8:49 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
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=20031204103041.21aefd8d.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 \
--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 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.