mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Lee <mukansai@emailplus.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Stephen Lee <mukansai@emailplus.org>,
	"Feldman, Scott" <scott.feldman@intel.com>,
	Harald Welte <laforge@netfilter.org>,
	netfilter-devel@lists.netfilter.org,
	linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@redhat.com>
Subject: Re: Extremely slow network with e1000 & ip_conntrack
Date: Fri, 05 Dec 2003 22:25:53 +0900	[thread overview]
Message-ID: <20031205222541.3427.MUKANSAI@emailplus.org> (raw)
In-Reply-To: <3FCF9497.3030708@pobox.com>

Hi,

Okay, I reproduced it with tg3 on 2.6.0-test11 as well, by turning on
TSO with ethtool.  So it does seem to be an incompatibility between TSO
& conntrack.

"David S. Miller" <davem@redhat.com> wrote:
> This workaround explains everything.  The TSO packets have to be
> "un-TSO'd" in order for netfilter to look at the packet and parse
> the contents.  This means copying all the data around, allocating
> several networking buffers, etc.

But, if netfilter needs to see all the contents in order to function,
shouldn't TSO break other parts of netfilter as well?  Why is only
conntrack affected?

Jeff Garzik <jgarzik@pobox.com> wrote:
> Regardless, the problem is identified -- when TSO+conntrack is present,
> we "TSO" net traffic then "un-TSO" it.

This "un-TSO"ing more or less defeats the purpose of TSO, right?  

> It's simply better to not use TSO at all, for this case.

If that is the case, I suppose so.

Thanks,
Stephen


  reply	other threads:[~2003-12-05 13:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
     [not found] <20031126174943.0AA5.MUKANSAI@emailplus.org>
     [not found] ` <20031129042551.A460.MUKANSAI@emailplus.org>
     [not found]   ` <20031130074532.0105.MUKANSAI@emailplus.org>
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=20031205222541.3427.MUKANSAI@emailplus.org \
    --to=mukansai@emailplus.org \
    --cc=davem@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=laforge@netfilter.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome