From: Ookhoi <ookhoi@humilis.net>
To: Ookhoi <ookhoi@humilis.net>
Cc: Florian Zwoch <zwoch@backendmedia.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: e1000 -> 82540EM on linux 2.6.0-test[45] very slow in one direction
Date: Fri, 3 Oct 2003 14:23:29 +0200 [thread overview]
Message-ID: <20031003122329.GA21532@favonius> (raw)
In-Reply-To: <20031003103025.GA20676@favonius>
Ookhoi wrote (ao):
> Florian Zwoch wrote (ao):
> > issue seems to partly solved. the e1000 driver seems to be ok!
> > i reconfigured my kernel and intentionally left out netfilter options.
> > after that my network performance was back to normal.
> >
> > netfilter was only compiled in the kernel. it was not used with any rules!
> >
> > so my wild guess would be that something with the netfilter code (i am
> > not 100% sure it was netfilter.. _maybe_ it was some small odd kernel
> > option i accidently enabled/disabled) is broken since test3 (again
> > uncertified. but i firstly noticed this switching from test3 to test4).
> I have netfilter enabled, and will try another -test6 kernel with
> netfilter not compiled in to see if that indeed makes a difference.
I can confirm now that disabling netfilter in 2.6.0-test6 makes the nic
perform oke wrt upload.
I (just like Florian) had no iptables rules active in the former
2.6.0-test6 kernel, but netfilter was compiled in.
next prev parent reply other threads:[~2003-10-03 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 10:25 e1000 -> 82540EM on linux 2.6.0-test[45] very slow in one direction Florian Zwoch
2003-10-01 8:02 ` Florian Zwoch
2003-10-01 8:02 ` Florian Zwoch
2003-10-03 10:30 ` Ookhoi
2003-10-03 12:23 ` Ookhoi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 18:27 Leech, Christopher
2003-10-04 6:49 ` Sander
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=20031003122329.GA21532@favonius \
--to=ookhoi@humilis.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=zwoch@backendmedia.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.